Duo cloud application

You must be signed in as a super administrator for this task.

Using Security Assertion Markup Language (SAML), your users can use their Google Cloud credentials to sign in to enterprise-cloud applications.

Set up SSO via SAML for Duo®

Step 1: Get configuration information from Duo
  1. Sign in to Duo with your Admin account.
  2. In the left navigation panel, click Administrators, then Admin Login Settings.
  3. In the Metadata for Configuring with Custom Identity Provider section, copy and save these two values:
    • Entity ID or Issuer ID
    • Assertion consumer service URL or single sign-on URL

Leave Duo open in the browser, you’ll return here in Step 3 to finish SAML configuration after getting information from the Google Admin console in the next step.

Step 2: Set up Google as a SAML identity provider (IdP)
  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenSAML apps.
  3. Click Add at the bottom right.
  4. Locate and click Duo in the application list.
  5. On the Google IDP Information page:
    • Copy and save the SSO URL and Entity ID.
    • Download the Certificate.
  6. Click Next.

    The Basic information window shows the Application name and Description seen by users.

  7. Click Next.
  8. On the Service Provider Details page, replace the default Entity ID and ACS URL with the corresponding values you copied from copied from Duo in Step 1.
  9. Click Finish.
Step 3: Set up Duo as a SAML 2.0 service provider (SP)
  1. Return to the browser window showing Duo Admin Login Settings.
  2. In the Authentication with SAML section, choose the desired authentication option for your organization.
  3. In SAML Identity Provider Settings, choose or enter the following information:
    • Identity provider: Custom Identity Provider
    • Configuration method:  Manual Entry
    • Entity ID or issuer ID:  the Entity ID you copied from Google in Step 2 above.
    • Assertion consumer service URL or single sign-on URL: the SSO URL you copied in Step 2.
    • Certificate: the certificate you downloaded in Step 2. 
  4. In Advanced SAML options, choose the following settings:
    • SHA-1 signatures: leave unchecked.
    • Signed elements: select Only responses must be signed.
  5. Click Save.
Step 4: Enable the Duo app
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenSAML apps.
  3. Select Duo.
  4. At the top right of the gray box, click Edit Service .

  5. To turn on or off a service for everyone in your organization, click On for everyone or Off for everyone, and then click Save.

  6. To turn on or off a service only for users in an organizational unit:

    1. At the left, select the organizational unit.
    2. Select On or Off.
    3. To keep the service turned on or off even when the service is turned on or off for the parent organizational unit, click Override.
    4. If the organization's status is already Overridden, choose an option:
      • Inherit—Reverts to the same setting as its parent.
      • Save—Saves your new setting (even if the parent setting changes).

    Learn more about organizational structure.

  7. (Optional) Turn on the service for a group of users.
    Use access groups to turn on a service for specific users within or across your organizational units. Learn more

  8. Ensure that your Duo user account email IDs match those in your Google domain.
Step 5: Verify that the SSO is working

Note: Before you can verify SSO for Duo, you need to request your organization’s SSO login URL from the Duo Support team.

  1. In a new browser window, go to your organization’s Duo login URL.
  2. Click Single Sign On.
  3. Enter your sign in email address and click Continue to Identity Provider. You should be automatically redirected to the Google sign-in page.
  4. Enter your Google sign in credentials.

    After your sign-in credentials are authenticated you're automatically redirected back to Duo.

Was this helpful?
How can we improve it?