Single Sign-On and Webex Control Hub

Single sign-on (SSO) is a session or user authentication process that permits a user to provide credentials to access one or more applications. The process authenticates users for all the applications that they are given rights to. It eliminates further prompts when users switch applications during a particular session.

The Security Assertion Markup Language (SAML 2.0) Federation Protocol is used to provide SSO authentication between the Cisco Webex cloud and your identity provider (IdP).


Cisco Webex Teams only supports the web browser SSO profile. In the web browser SSO profile, Cisco Webex Teams supports the following bindings:

  • SP initiated POST -> POST binding

  • SP initiated REDIRECT -> POST binding

NameID Format

The SAML 2.0 Protocol supports several NameID formats for communicating about a specific user. Cisco Webex Teams supports the following NameID formats.

  • urn:oasis:names:tc:SAML:2.0:nameid-format:transient

  • urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified

  • urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

In the metadata that you load from your IdP, the first entry is configured for use in Cisco Webex.

Integrate Cisco Webex Control Hub with Microsoft Azure

The configuration guides show a specific example for SSO integration but do not provide exhaustive configuration for all possibilities. For example, the integration steps for nameid-format urn:oasis:names:tc:SAML:2.0:nameid-format:transient are documented. Other formats such as urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified or urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress will work for SSO integration but are outside the scope of our documentation.

Set up this integration for users in your Cisco Webex organization (including Cisco Webex Teams, Cisco Webex Meetings, and other services administered in Cisco Webex Control Hub). If your Webex site is integrated in Cisco Webex Control Hub, the Webex site inherits the user management. If you can't access Cisco Webex Meetings in this way and it is not managed in Cisco Webex Control Hub, you must do a separate integration to enable SSO for Cisco Webex Meetings. (See Configure Single Sign-On for Webex for more information in SSO integration in Site Administration.)

Before you begin

For SSO and Cisco Webex Control Hub, IdPs must conform to the SAML 2.0 specification. In addition, IdPs must be configured in the following manner:
  • Set the NameID Format attribute to urn:oasis:names:tc:SAML:2.0:nameid-format:transient

  • Configure a claim on the IdP to include the uid attribute name with a value that is mapped to the attribute that is chosen in Cisco Directory Connector or the user attribute that matches the one that is chosen in the Cisco Webex identity service. (This attribute could be E-mail-Addresses or User-Principal-Name, for example.) See the custom attribute information in for guidance.

  • Use a supported browser: we recommend the latest version of Mozilla Firefox or Google Chrome.

  • Disable any popup blockers in your browser.

In Azure Active Directory, provisioning is only supported in manual mode. This document only covers single sign-on (SSO) integration.

Download the Cisco Webex Metadata to your Local System


From the customer view in, go to Settings, and then scroll to Authentication.


Click Modify, click Integrate a 3rd-party identity provider. (Advanced), and then click Next.


Download the metadata file.

The Cisco Webex metadata filename is idb-meta-<org-ID>-SP.xml.

Configure Single-Sign On Application Settings in Azure

Before you begin

  • See What is Azure Active Directory to undestand the IdP capabilities in Azure Active Directory.

  • Configure Azure Active Directory.

  • Create local users or synchronize with an on-premises active directory system.

  • Open the Cisco Webex metadata file that you downloaded from Cisco Webex Control Hub.


Sign in to the Azure portal at with your administrator credentials.


Go to Azure Active Directory for your organization.


Go to Enterprise Applications and then click Add.


Click Add an application from the gallery.


In the search box, type Cisco Webex.


In the results pane, select Cisco Webex, and then click Add to add the application.

A message appears that says the application was added successfully.


Configure Single-Sign On:

  1. After you create the application agreement, go to the Single sign-on tab, and then under Select a single-sign on method, choose SAML.

  2. On the Set up Single Sign-On with SAML page, click Edit icon to open Basic SAML Configuration.

  3. Click Upload metadata file and then choose the metadata file that you downloaded from Cisco Webex Control Hub.

    Some fields are automatically filled out for you.

  4. Copy the Reply URL value and paste it into Sign on URL, and then save your changes.


Scroll to Users Attributes & Claims (number 2 in Azure admin), click the pencil icon, and then click Add new claim


Cisco Webex expects to have an attribute called uid that normally matches the email address of the user (in Azure, it normally maps to userprincipalname). You must map the attribute to the one that is used to create the user in Webex Control Hub.


On the Manage user claims flyout pane, for Name, enter uid, and for Source attribute, choose the user attribute (for this step, we'll use user.userprincipalname, the most commonly used attribute). Save your changes.


On the Users Attributes & Claims page, the attributes aside from the one that you configured in this step are not relevant to this integration. You can choose to delete them or just leave them on this screen.


Go to Manage > Users and groups, and then choose the applicable users and groups that you want to grant access to Cisco Webex Teams.


On the Set up Single Sign-On with SAML page, in the SAML Signing Certificatesection, click Download to download the Federation Metadata XML and save it on your computer.

Import the IdP Metadata and Enable Single Sign-On After a Test

After you export the Cisco Webex metadata, configure your IdP, and download the IdP metadata to your local system, you are ready to import it into your Cisco Webex organization from Control Hub.

Before you begin

Do not test SSO integration from the identity provider (IdP) interface. We only support Service Provider-initiated (SP-initiated) flows, so you must use the Control Hub SSO test for this integration.


Choose one:

  • Return to the Cisco Webex Control Hub – Export Directory Metadata page in your browser, and then click Next.
  • If Control Hub is no longer open in the browser tab, from the customer view in, go to Settings, scroll to Authentication, choose Integrate a third-party identity provider (Advanced), and then click Next on trusted metadata file page (because you already did it before).

On the Import IdP Metadata page, either drag and drop the IdP metadata file onto the page or use the file browser option to locate and upload the metadata file. Click Next.

If the metadata isn't signed, is signed with a self-signed certificate, or is signed with a private enterprise certificate authority (CA), we recommend that you use require certificate signed by a certificate authority in Metadata (more secure). If the certificate is self-signed, you need to choose the less secure option.


Select Test SSO Connection, and when a new browser tab opens, authenticate with the IdP by signing in.


If you receive an authentication error there may be a problem with the credentials. Check the username and password and try again.

A Webex Teams error usually means an issue with the SSO setup. In this case, walk through the steps again, especially the steps where you copy and paste the Control Hub metadata into the IdP setup.


Return to the Control Hub browser tab.

  • If the test was successful, select This test was successful. Enable Single Sign-On option and click Next.
  • If the test was unsuccessful, select This test was unsuccessful. Disable Single Sign-On option and click Next.

What to do next

Use the procedures in Synchronize Azure Active Directory Users into Cisco Webex Control Hub if you want to do user provisioning out of Azure AD into the Webex cloud.

You can follow the procedure in Suppress Automated Emails to disable emails that are sent to new Webex Teams users in your organization. The document also contains best practices for sending out communications to users in your organization.

Troubleshoot Azure Active Directory Integration

When doing the SAML test, make sure that you use Mozilla Firefox and you install the SAML tracer from

Check the assertion that comes from Azure to make sure that it has the correct nameid format and has an attribute uid that match a user in Cisco Webex Teams.