Add two-factor authentication and flexible security policies to Cisco Webex SSO logins with Duo Single-Sign On, our cloud-hosted SAML 2.0 identity provider, complete with inline self-service enrollment and Duo Prompt.
Duo Federal customers or those looking for an on-premises SSO solution: try Duo Protection for Cisco Webex (with Control Hub) with Duo Access Gateway.
If your administrator login URL is https://admin.webex.com/login continue below. If your administrator login URL for Cisco Webex is https://yourdomain.webex.com/admin, please see our generic service provider application.
These Webex clients support Trusted Endpoints:
As business applications move from on-premises to cloud hosted solutions, users experience password fatigue due to disparate logons for different applications. Single sign-on (SSO) technologies seek to unify identities across systems and reduce the number of different credentials a user has to remember or input to gain access to resources.
While SSO is convenient for users, it presents new security challenges. If a user's primary password is compromised, attackers may be able to gain access to multiple resources. In addition, as sensitive information makes its way to cloud-hosted services it is even more important to secure access by implementing two-factor authentication.
Duo Single Sign-On is our cloud-hosted SSO product which layers Duo's strong authentication and flexible policy engine on top of Webex logins using the Security Assertion Markup Language (SAML) 2.0 authentication standard. Duo Single Sign-On acts as an identity provider (IdP), authenticating your users using existing on-premises Active Directory (AD) or any SAML 2.0 IdP and prompting for two-factor authentication before permitting access to Webex.
Duo Single Sign-On is available in Duo Beyond, Duo Access, and Duo MFA plans, which also include the ability to define policies that enforce unique controls for each individual SSO application. For example, you can require that Salesforce users complete two-factor authentication at every login, but only once every seven days when accessing Webex. Duo checks the user, device, and network against an application's policy before allowing access to the application.
Once you have your SSO authentication source working, continue to the next step of creating the Webex application in Duo.
Log into Control Hub as an administrative user.
Click on Settings in the left-hand navigation bar.
Next to “Authentication” click Modify. A pop-up will appear with new options.
On the “Single Sign-On” page select Integrate a 3rd-party identity provider. (Advanced) and click Next.
On the “Export Directory Metadata” page click Download Metadata File. You'll need this file later.
Leave this page open in a tab, you'll return to it later.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the entry for Cisco Webex (with Control Hub) with a protection type of "2FA with SSO hosted by Duo (Single Sign-On)" in the applications list. Click Protect to the far-right to start configuring Cisco Webex (with Control Hub). See Protecting Applications for more information about protecting applications in Duo and additional application options. You'll need the information on the Cisco Webex (with Control Hub) page under Metadata later.
Upload the metadata file you downloaded earlier to the XML File section.
Webex uses the Mail attribute when authenticating. We've mapped the <Email Address> bridge attribute to Duo Single Sign-On supported authentication source attributes as follows:
|Bridge Attribute||Active Directory||SAML IdP|
If you are using a non-standard email attribute for your authentication source, check the Custom attributes box and enter the name of the attribute you wish to use instead.
You can adjust additional settings for your new SAML application at this time — like changing the application's name from the default value, enabling self-service, or assigning a group policy.
Scroll to the bottom of the page and click the Save button.
The XML File section should now display a green checkmark showing that it is configured. You can upload a new XML file in the future to override the existing one.
The new Universal Prompt provides a simplified and accessible Duo login experience for web-based applications, offering a redesigned visual interface with security and usability enhancements.
|Universal Prompt||Traditional Prompt|
We've already updated the Duo Cisco Webex application hosted in Duo's service to support the Universal Prompt, so there's no action required on your part to update the application itself. You can activate the Universal Prompt experience for users of new and existing Duo Cisco Webex applications from the Duo Admin Panel.
Before you activate the Universal Prompt for your application, it's a good idea to read the Universal Prompt Update Guide for more information about the update process and the new login experience for users.
Activation of the Universal Prompt is a per-application change. Activating it for one application does not change the login experience for your other Duo applications.
The "Universal Prompt" area of the application details page shows that this application is "New Prompt Ready", with these activation control options:
Enable the Universal Prompt experience by selecting Show new Universal Prompt, and then scrolling to the bottom of the page to click Save.
Once you activate the Universal Prompt, the application's Universal Prompt status shows "Update Complete" here and on the Universal Prompt Update Progress report.
Should you ever want to roll back to the traditional prompt, you can return to this setting and change it back to Show traditional prompt.
Click the See Update Progress link to view the Universal Prompt Update Progress report. This report shows the update availability and migration progress for all your Duo applications in-scope for Universal Prompt support. You can also activate the new prompt experience for multiple supported applications from the report page instead of visiting the individual details pages for each application.
Return to Control Hub as an administrative user.
Continuing from where you were earlier on the “Export Directory Metadata” page click Next.
On “Import IdP Metadata” under “Signing of Metadata” select Allow self-signed certificate in Metadata.
Click Download XML next to the "IdP Metadata file" button on the Webex application's page in the Duo Admin Panel under Downloads to download the Duo Single Sign-On XML file. On the Webex administrative page upload the XML metadata file you downloaded from Duo. Click Next.
On the “Test SSO Setup” page click Test SSO Connection. A new page will open and you’ll be redirected to login with Duo Single Sign-On by completing primary authentication and Duo second-factor. Upon successful login you’ll be taken to a page that says “Single Sign-on succeeded.” Close this window and return to the Control Hub page.
As long as the authentication was successful select The test was successful. Enable Single Sign On. and click Next. If it was not successful, double-check instructions and settings. Do not continue until you get a successful test authentication.
Once the settings successfully save you’ll be returned to the “Settings” page and SSO will be enabled for Webex.
Learn more about Webex SSO at Webex Help.
You can log on by navigating to Webex Login. Type your e-mail address the text field and click Next. This redirects you to Duo Single Sign-On to enter your primary directory logon information. For example, this is the SSO login page when your authentication source is Active Directory.
Successful verification of your primary credentials redirects you to Duo. Complete Duo two-factor authentication when prompted and then you'll return to Webex to complete the login process.
*Universal Prompt experience shown.
Congratulations! Your Webex users now authenticate using Duo Single Sign-On.
Users can also log in using their desktop and mobile app clients for Webex Meetings and Webex Teams.
To minimize additional Duo two-factor prompts when switching between Webex and your other Duo Single Sign-On SAML applications, be sure to apply a shared "Remembered Devices" policy to your SAML applications.