AWS IAM Identity Center (successor to AWS SSO) Integration Guide for Cisco Webex
Introduction
This document helps you configure IAM Identity Center to facilitate single sign-on (SSO) for Cisco Webex using SAML.
Topics
Prerequisites
You’ll need the following to set up SSO access to Cisco Webex:
-
Access to the IAM Identity Center console with permissions to manage applications.
-
An Cisco Webex account with admin permissions to configure SAML SSO.
Setup instructions
- On the Configure page, in the Details section, fill in the Display name and the Description(optional) of the application.
Note
We suggest that you choose a unique display name if you plan to have more than one of the same application.
Note
Cisco Webex supports SP initiated flow only.
-
Login to your Cisco Webex account as an administrator (example: https://admin.webex.com).
-
In the left navigation pane, choose Settings.
-
On the settings page, scroll down to Authentication and choose modify below Single Sign-On.
-
Choose the option Integrate a 3rd-party identity provider (Advanced) then choose Next.
-
Choose Download Metadata File.
-
Go back to the IAM Identity Center console page where you are configuring the Application.
-
Under Application properties, Insert the value, ensure you replace DOMAINNAME with your DOMAINNAME:
Field | Value |
---|---|
Application start URL | https://DOMAINNAME.webex.com/mw3300/mywebex/default.do?siteurl=DOMAINNAME&viewFrom=modern |
&login_return_url=https://DOMAINNAME.webex.com/webappng/sites/DOMAINNAME/dashboard?siteurl=DOMAINNAME |
- Edit the Cisco Webex metadata file and find entityID and location:
entityID=https://idbroker.webex.com/ID Location=https://idbroker.webex.com/idb/Consumer/metaAlias/ID/sp
- Under Application metadata, select If you don’t have a metadata file, you can manually type your metadata values. Then insert these values:
Field | Value |
---|---|
Application ACS URL | https://idbroker.webex.com/idb/Consumer/metaAlias/ID/sp |
Application SAML audience | https://idbroker.webex.com/ID |
As you can see the Location attribute is entered in the Application ACS URL field and the entityID attribute entered in the Application SAML audience.
-
Choose Save Changes.
-
Assign a user to the application in IAM Identity Center.
-
Go back to the Cisco Webex administration console and choose Next on the Export Directory Metadata page.
-
Download IAM Identity Center metadata file.
-
Below Import IdP Metadata choose file browser and select the previously downloaded IAM Identity Center metadata file.
-
On the Test SSO setup page, choose Test SSO Connection.
-
Type the credentials of a user assigned to the application in the IAM Identity Center console.
-
Choose Sign In.
-
You will now see the following message Single Sign-on succeeded.
-
Go back to the Cisco Webex administration console, choose The test was successful. Enable Single Sign On., then choose Save.
Verification
Use the following sections to verify the SSO integration.
Note
Ensure that the user performing the verification is logged out of both IAM Identity Center and the application before performing the steps in each section.
Verifying Service Provider Initiated SSO from Cisco Webex
-
Browse to the Cisco Webex login page for your application. The login URL is of the form https://DOMAINNAME.webex.com
-
Choose Sign in.
-
Type the email address of a user assigned to the application in the IAM Identity Center console, then choose Next.
-
Type the credentials of a user assigned to the application in the IAM Identity Center console, then choose Next.
-
Choose Sign In.
-
On the Cisco Webex home page, verify that both Cisco Webex and IAM Identity Center are logged in with the same user.
Troubleshooting
If sign in was not successful, please see the troubleshooting steps.
Verifying SSO from IAM Identity Center
-
Access the AWS access portal using the credentials of a user assigned to the Cisco Webex application.
-
In the list of applications, choose Cisco Webex to initiate a login to Cisco Webex.
-
Type the email address of a user assigned to the application in the IAM Identity Center console, then choose Next.
-
If login was successful you will be signed-in to the Cisco Webex account.
Troubleshooting
If sign in was not successful, please see the troubleshooting steps.
Troubleshooting
Error | Issue | Solution |
---|---|---|
Other | When IAM Identity Center creates a SAML Assertion for a user, it uses the value of the 'email' field (if they are present) from the connected directory to populate the 'Email' in the SAML assertion. Many service providers expect these attributes to contain the user’s email address. By default your directory is configured to send 'windowsUPN' in both fields. | Your directory may be configured to contain the users email in the 'Email' attribute instead. If so, you may need to change this in your Connected directory settings. |
For general troubleshooting problems, please refer to Troubleshooting Guide.
User Provisioning Types
There are two user provisioning you need to aware of:
-
Preprovisioned users
Preprovisioned users, means users must already exist in the downstream SaaS application. For instance, you may need to create SaaS users with the same subject as the AD users.
-
JIT users
JIT (or Just-In-Time) users, means users do not necessarily exist in the downstream SaaS application, and will be provisioned/created/registered the first time the user federates. You may need to enable JIT option in your SaaS application for the AD domain.