Duo Single Sign-On for Google Chrome Enterprise

About Duo Single Sign-On

Duo Single Sign-On is our cloud-hosted SSO product which layers Duo's strong authentication and flexible policy engine on top of Google Chrome Enterprise logins using OpenID Connect (OIDC) authentication standards. Duo Single Sign-On acts as an OpenID provider (OP), authenticating Duo-hosted users or users in external authentication sources, like an existing on-premises Active Directory (AD) or any SAML 2.0 IdP. Duo's strong multi-factor authentication further verifies users before permitting access to Google Chrome Enterprise.

Duo Single Sign-On is available in Duo Premier, Duo Advantage, and Duo Essentials plans, which also include the ability to define policies that enforce unique controls for each individual SSO application. For example, you can require that Google Chrome Enterprise users complete two-factor authentication at every login, but only once every seven days when accessing a different application. Duo checks the user, device, and network against an application's policy before allowing access to the application.

Configure Single Sign-On

Before configuring Google Chrome Enterprise with Duo SSO using OIDC authentication, you'll first need to complete Duo SSO configuration, which may include setting up a working external authentication source if your organization will not store your user identities in Duo.

Once you complete initial Duo SSO configuration, continue to the next step of creating the Google Chrome Enterprise application in Duo.

When configuring an application to be protected with Duo Single Sign-On you'll need to send attributes from Duo Single Sign-On to the application. Duo and Active Directory authentication sources will work with no additional setup, but if you used a SAML identity provider as your authentication source please verify that you configured it to send the correct SAML attributes.

Below you can see the default authentication source attribute mappings.

Default Attribute	Active Directory	SAML IdP
<Username>	sAMAccountName	Username
<Email Address>	mail	Email
<Display Name>	displayName	DisplayName
<First Name>	givenName	FirstName
<Last Name>	sn	LastName
<Entra Federated User ID>	mS-DS-ConsistencyGuid	EntraImmutableID

Create the Google Chrome Enterprise Application in Duo

1. Log in to the Duo Admin Panel and navigate to Applications → Application Catalog.

2. Locate the entry for Google Chrome Enterprise with the "SSO" label in the catalog. Click the + Add button to start configuring Google Chrome Enterprise. See Protecting Applications for more information about protecting applications with Duo and additional application options. You'll need the information on the Google Chrome Enterprise page under Metadata later.

3. No users can log in to new applications until you grant access. Update the User access setting to grant access to this application to users in selected Duo groups, or to all users. Learn more about user access to applications. If you do not change this setting now, be sure to update it so that your test user has access before you test your setup.

4. The Metadata section contains OpenID provider information about Duo Single Sign-On you will provide to Google Chrome Enterprise at a later configuration step.

5. Scopes are used by Google Chrome Enterprise during authentication to authorize access to a user's details. Each scope returns a set of user attributes (claims) that must be mapped to IdP attributes. When an application sends an OIDC request to Duo SSO, the response sends only the claims from the requested scopes.

   We've automatically enabled the following scopes and mapped the listed attributes. You can change the attribute sent from your authentication source by modifying the IdP Attribute name related to each claim:

   • Profile Scope:

     IdP Attribute	Claim
     <Display Name>	name

   • Email Scope:

     IdP Attribute	Claim
     <Email Address>	email

   

6. You can adjust additional settings for your new SSO application at this time — like changing the application's name from the default value, enabling self-service, or assigning a group policy.

7. Keep the Duo Admin Panel tab open. You will come back to it later.

Duo Universal Prompt

The Duo 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

The Duo Google Chrome Enterprise application supports the Universal Prompt by default, so there's no additional action required on your part to start using the newest authentication experience.

Activate Universal Prompt

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. Universal Prompt is already activated for new Google Chrome Enterprise applications at creation.

The "Universal Prompt" area of the application details page shows that this application's status is "Activation complete", with these activation control options:

• Show traditional prompt: Your users experience Duo's traditional prompt via redirect when logging in to this application.
• Show new Universal Prompt: (Default) Your users experience the Universal Prompt via redirect when logging in to this application.

The application's Universal Prompt status shows "Activation complete" both here and on the Universal Prompt Update Progress report.

For the time being, you may change this setting to Show traditional prompt to use the legacy experience. Keep in mind that support for the traditional Duo prompt ended for the majority of applications in March 2024. This option will be removed in the future.

Universal Update Progress

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. 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.

Configure Google Chrome Enterprise

1. Log into your Google Chrome Enterprise account as an administrator.

2. In the sidebar menu, navigate to Chrome browser → Connectors.

3. Click NEW PROVIDER CONFIGURATION. The "Set up a provider" window opens.

4. Scroll down to "Generic OIDC" and click SET UP. The "Generic OIDC configuration" window opens.

5. Enter a unique name for your OIDC configuration into the Configuration name field.

6. Return to the Duo Admin Panel. Under "Metadata", copy the Authorization URL and paste it into the Google Chrome Enterprise Authorization endpoint field.

7. Return to the Duo Admin Panel. Copy the Client ID and paste it into the Google Chrome Enterprise Client id field.

8. In Google Chrome Enterprise, type email into the Email claim field.

9. Type enrollment_token into the Enrollment token claim field.

10. Return to the Duo Admin Panel. Copy the Issuer URL and paste it into the Google Chrome Enterprise Issuer field.

11. Return to the Duo Admin Panel. Copy the Client Secret and paste it into the Google Chrome Enterprise Client secret field.

12. In Google Chrome Enterprise, click ADD CONFIGURATION. The "Generic OIDC configuration" window closes.

13. Return to the Duo Admin Panel. Scroll down to "Relying Party" and make sure the Allow PKCE only authorization checkbox is selected.

14. In the Duo Admin Panel, type https://chromeenterprise.google/profile-enrollment/register-handler into the Sign-In Redirect URLs field.

    

15. Scroll down to "OIDC Response" and click the Enable Claim Transformations checkbox.

16. In the Transformation Rules field, type the text listed below on three separate lines. See the image below for an example.

    • use "<Username>"

    • remove additional_attr="<Username>"

    • append text=""

17. Click the Scope drop-down menu and select profile.

18. In the Claim field, type enrollment_token.

    

19. Return to Google Chrome Enterprise. In the sidebar menu, navigate to Chrome browser → Managed browsers. The "Managed Browsers" page opens.

20. In the "Managed Browsers" sidebar menu, click the organizational unit that you want to create the enrollment token for.

21. Click the Enroll tab. The "Enroll new Chrome browsers in SSO Team" pop-up window opens.

22. Copy the Token and paste it into the Duo Admin Panel, Transformation Rules field, between the quotation marks on the last line. See the image below for an example.

    

23. In the Duo Admin Panel, scroll down to the bottom of the page and click Save.

24. Return to Google Chrome Enterprise. Under "Generic OIDC" next to your OIDC configuration name, click DETAILS. The "Generic OIDC" window opens.

25. Under "Provider configuration", make note of your Enrollment URL. You will need it later.

    Example: https://chromeenterprise.google/profile-enrollment/register?configuration=ABcde23FghI4JKLM

Using SSO

To log on to Google Chrome Enterprise SSO, do the following:

1. Navigate to the Google Chrome Enterprise enrollment URL that you noted earlier. You will be automatically redirected to Duo Single Sign-On to begin authentication.

   Example: https://chromeenterprise.google/profile-enrollment/register?configuration=ABC123efg456HIJ789

2. After you authenticate with Duo Single Sign-On, the Set up a new profile pop-up window opens.

3. Click Continue to set up your Google Chrome profile. The You're all set! pop-up window opens.

4. Click Continue.

Duo-hosted or Active Directory Login

With Duo or Active Directory as the Duo SSO authentication source, enter the primary username (email address) on the Duo SSO login page and click or tap Next.

Enter the Duo or AD primary password and click or tap Log in to continue.

When using Duo Passwordless you won't need to enter a password, and will proceed directly to Duo authentication.

SAML Login

With another SAML identity provider as the Duo SSO authentication source, Duo SSO immediately redirects the login attempt to that SAML IdP for primary authentication. Users do not see the Duo SSO primary login screen.

Duo Authentication

Successful verification of your primary credentials by Duo, Active Directory, or a SAML IdP redirects back to Duo. Complete Duo two-factor authentication when prompted and then you'll return to Google Chrome Enterprise to complete the login process.

* Universal Prompt experience shown.

Google Chrome Enterprise supports SP-initiated authentication only, meaning that you must start your SSO login from that application's sign-in page. You won't be able to add as an application tile in Duo Central for IdP-initiated logins.

Congratulations! Your Google Chrome Enterprise users now authenticate using Duo Single Sign-On.

See the full user login experience, including expired password reset (available for Active Directory authentication sources) in the Duo End User Guide for SSO.

Grant Access to Users

If you did not already grant user access to the Duo users you want to use this application be sure to do that before inviting or requiring them to log in with Duo.

Enable Remembered Devices

To minimize additional Duo two-factor prompts when switching between and your other Duo Single Sign-On SAML applications, be sure to apply a shared "Remembered Devices" policy to your SAML applications.

Troubleshooting

Need some help? Try searching our Knowledge Base articles or Community discussions. For further assistance, contact Support.