You can configure a single sign-on (SSO) integration between a Control Hub customer organization and a deployment that uses Microsoft Azure as an identity provider (IdP).
Single sign-on and 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 Webex cloud and your identity provider (IdP).
Webex App only supports the web browser SSO profile. In the web browser SSO profile, Webex App supports the following bindings:
SP initiated POST -> POST binding
SP initiated REDIRECT -> POST binding
The SAML 2.0 Protocol supports several NameID formats for communicating about a specific user. Webex App supports the following NameID formats.
In the metadata that you load from your IdP, the first entry is configured for use in Webex.
Integrate 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
Set up this integration for users in your Webex organization (including Webex App, Webex Meetings, and other services administered in Control Hub). If your Webex site is integrated in Control Hub, the Webex site inherits the user management. If you can't access Webex Meetings in this way and it is not managed in Control Hub, you must do a separate integration to enable SSO for Webex Meetings. (See Configure Single Sign-On for Webex for more information in SSO integration in Site Administration.)
Before you begin
For SSO and Control Hub, IdPs must conform to the SAML 2.0 specification. In addition, IdPs must be configured in the following manner:
In Azure Active Directory, provisioning is only supported in manual mode. This document only covers single sign-on (SSO) integration.
Download the Webex metadata to your local system
From the customer view in https://admin.webex.com, go to , and then scroll to Authentication, and then toggle on the Single sign-on setting to start the setup wizard.
Choose the certificate type for your organization:
Download the metadata file.
The Webex metadata filename is idb-meta-<org-ID>-SP.xml.
Configure SSO application settings in Azure
Before you begin
See What is Azure Active Directory to understand 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 Webex metadata file that you downloaded from Control Hub.
There is a related tutorial on the Microsoft documentation site.
Sign in to the Azure portal at https://portal.azure.com with your administrator credentials.
If you cannot see the Azure Active Directory icon, click More services.
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 Create to add the application.
To make sure that the Webex application you've added for single sign-on doesn't show up in the user portal, open the new application. Under Manage, click Properties, and set Visible to users? to No.
We don't support making Webex app visible to users.
Configure Single-Sign On:
Go to Manage > Users and groups, and then choose the applicable users and groups that you want to grant access to Webex App.
On the Set up Single Sign-On with SAML page, in the SAML Signing Certificate section, 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 Webex metadata, configure your IdP, and download the IdP metadata to your local system, you are ready to import it into your 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.
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.
You should use the More secure option, if you can. This is only possible if your IdP used a public CA to sign its metadata.
In all other cases, you must use the Less secure option. This includes if the metadata is not signed, self-signed, or signed by a private CA.
Select Test SSO setup, and when a new browser tab opens, authenticate with the IdP by signing in.
Return to the Control Hub browser tab.
What to do next
Use the procedures in Synchronize Okta Users into Cisco Webex Control Hub if you want to do user provisioning out of Okta into the Webex cloud.
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 App users in your organization. The document also contains best practices for sending out communications to users in your organization.
Troubleshoot Azure integration
When doing the SAML test, make sure that you use Mozilla Firefox and you install the SAML tracer from https://addons.mozilla.org/en-US/firefox/addon/saml-tracer/
Check the assertion that comes from Azure to make sure that it has the correct nameid format and has an attribute uid that matches a user in Webex App.