Webex Meetings desktop clients do not currently 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 Access Gateway (DAG), our on-premises SSO product, layers Duo's strong authentication and flexible policy engine on top of Webex Meetings logins using the Security Assertion Markup Language (SAML) 2.0 authentication standard. Duo Access Gateway acts as an identity provider (IdP), authenticating your users using existing on-premises or cloud-based directory credentials and prompting for two-factor authentication before permitting access to Webex Meetings.
Duo Access Gateway is included in the 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 Meetings. Duo checks the user, device, and network against an application's policy before allowing access to the application.
Add the attributes from the table below that correspond to the Duo attributes Mail attribute, Username attribute, Last name attribute, and First name attribute in the "Attributes" field when configuring your Active Directory or OpenLDAP authentication source in the DAG admin console, separated by a comma. For example, if Active Directory is your authentication source, enter mail,sAMAccountName,sn,givenName in the "Attributes" field.
|Duo Attribute||Active Directory||OpenLDAP|
|First name attribute||givenName||gn|
|Last name attribute||sn||sn|
If your organization uses other directory attributes than the ones listed here then enter those attribute names instead. If you've already configured the attributes list for another cloud service provider, append the additional attributes not already present to the list, separated by a comma.
After completing the initial DAG configuration steps, click Applications on the left side of the Duo Access Gateway admin console.
Scroll down the Applications page to the Metadata section. This is the information you need to provide to Webex Meetings when configuring SSO. Click the Download Certificate link to obtain the token signing certificate (the downloaded file is named "dag.crt").
Contact your Webex Meetings Customer Success Manager to enable SSO for SAML 2.0 on your Webex Meetings account.
Important: Once SSO is enabled for your account it will disable normal Webex Meetings authentication except for the administrative console.
Add the Duo Access Gateway as a new single sign-on provider for Webex Meetings.
Log on to the Webex Meetings admin console by going to https://yourdomain.webex.com/admin
Click on Configuration -> Common Site Settings -> SSO Configuration located on the left-hand navigation menu.
Click on Site Certificate Manager and then upload the dag.crt file you downloaded from the DAG admin console “Application” page earlier. Click OK and verify the certificate was loaded properly. Click Close.
Verify that Federation Protocol is set to SAML 2.0. If not, contact your Webex Meetings Customer Success Manager.
Choose SP Initiated for the SSO Profile setting.
If Webex SAML Issuer (SP ID) is not set to http://www.webex.com, update the field so that it is.
Copy the Entity ID information from the Duo Access Gateway admin console Metadata display and paste it into the Webex Meetings Issuer for SAML (IdP ID) field.
Copy the SSO URL information from the Duo Access Gateway admin console Metadata display and paste it into the Webex Meetings Customer SSO Service Login URL field.
Choose Email address from the dropdown for NameID Format.
Delete the current text in the field for AuthnContextClassRef and replace it with:
Check the box for Single Logout. Copy the Logout URL information from the Duo Access Gateway admin console Metadata display and paste it into the Webex Meetings Customer SSO Service Logout URL field.
Webex Meetings offers other settings regarding user account creation and automatic account updating. You may enable these options at this time.
After you've entered all the required information click Update.
Learn more about Webex Meetings SSO at Webex Meetings Help.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the entry for Cisco Webex Meetings (with Site Admin) with a protection type of "2FA with SSO self-hosted (Duo Access Gateway)" in the applications list. Click Protect to the far-right to start configuring Cisco Webex Meetings (with Site Admin). See Protecting Applications for more information about protecting applications in Duo and additional application options.
Enter the subdomain used when logging into your company’s Webex Meetings portal as the Subdomain. For example, if your Webex login URL is https://yourdomain.webex.com then enter yourdomain.
Webex Meetings uses the Mail attribute, Username attribute, First name attribute, and Last name attribute when authenticating. We've mapped those to DAG supported authentication source attributes as follows:
|Duo Attribute||Active Directory||OpenLDAP||SAML IdP||Azure|
|First name attribute||givenName||gn||givenName||given_name||givenName|
|Last name attribute||sn||sn||sn||family_name||surname|
If you are using non-standard attributes for your authentication source, check the Custom attributes box and enter the names of the attributes you wish to use instead.
Click Save Configuration to generate a downloadable configuration file.
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 — or come back and change the application's policies and settings after you finish SSO setup. If you do update any settings, click the Save Changes button when done.
Click the Download your configuration file link to obtain the Webex Meetings application settings (as a JSON file).
Important: This file contains information that uniquely identifies this application to Duo. Secure this file as you would any other sensitive or password information. Don't share it with unauthorized individuals or email it to anyone under any circumstances!
Before you do this, verify that you updated the "Attributes" list for your Duo Access Gateway authentication source as specified here.
Return to the Applications page of the DAG admin console session.
Click the Choose File button in the "Add Application" section of the page and locate the Webex Meetings SAML application JSON file you downloaded from the Duo Admin Panel earlier. Click the Upload button after selecting the JSON configuration file.
The Webex Meetings SAML application is added.
You can log on to Webex Meetings using your organization’s domain login page e.g. https://yourdomain.webex.com. Clicking Log In redirects you to the Duo Access Gateway login page. Enter your primary directory logon information, approve Duo two-factor authentication, and get redirected back to the Webex Meetings site after authenticating.
Congratulations! Your Webex Meetings users now authenticate using Duo Access Gateway.
If you plan to permit use of WebAuthn authentication methods (security keys, U2F tokens, or Touch ID), Duo recommends enabling hostname whitelisting for this application and any others that show the inline Duo Prompt before onboarding your end-users.
Microsoft's Active Directory Federation Services (AD FS) is a popular choice for SSO because it easily integrates with the AD identity store many organizations already have deployed. Duo's support for cloud applications and SSO drops in to an existing AD FS installation to provide secondary authentication after a user passes primary authentication (successful Active Directory logon).
If you don't already have AD federation running the first step is to install and configure Microsoft AD FS in your organization. Deployment Guides for AD FS versions 2.1, and 3.0/4.0 are available from Microsoft.
Once your AD FS services are up and running, the second step is to configure the SSO partnership between your AD FS service and the external cloud resource, in this case Webex Meetings. Learn more about configuring Webex Meetings SSO with AD FS at the Webex Meetings Help site.
After you have successfully configured and tested AD FS SSO login to Webex Meetings using your AD domain credentials, you can then install the Duo AD FS integration. AD FS protection is included with Duo's paid plans.
With the Duo integration for AD FS installed, users pass primary authentication to the AD FS service as usual. Once primary authentication succeeds, users are forwarded to the Duo service for secondary authentication. After approving logon using one of Duo's authentication methods, the user is fully logged in to Webex Meetings.
Using a third-party SSO provider for cloud application access? Duo partners with leading cloud SSO providers like Okta and OneLogin to secure access with our strong and flexible authentication platform.