Duo Single Sign-On for MongoDB Data Access

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 MongoDB Data Access logins using the Security Assertion Markup Language (SAML) 2.0 or OpenID Connect (OIDC) authentication standards. Duo Single Sign-On acts as an OpenID provider (OP), 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 MongoDB Data Access.

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 Salesforce users complete two-factor authentication at every login, but only once every seven days when accessing MongoDB Data Access. Duo checks the user, device, and network against an application's policy before allowing access to the application.

Configure Single Sign-On

Before configuring MongoDB Data Access with Duo SSO using OpenID Connect (OIDC) authentication you'll first need to configure a working authentication source.

Once you have your SSO authentication source working, continue to the next step of creating the MongoDB Data Access 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. Active Directory 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.

These default attributes automatically map certain attributes from your authentication source.

Create the MongoDB Data Access Application in Duo

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

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

3. No active Duo 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.

   This setting only applies to users who exist in Duo with "Active" status. This does not affect application access for existing users with "Bypass" status, existing users for whom the effective Authentication Policy for the application specifies "Bypass 2FA" or "Skip MFA", or users who do not exist in Duo when the effective New User Policy for the application allows access to users unknown to Duo without MFA.

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

5. Scopes are used by MongoDB Data Access 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
     <First Name>	given_name
     <Last Name>	family_name
     <Display Name>	name
     <groups>	groups

   • Email Scope:

     IdP Attribute	Claim
     <Email>	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 MongoDB Data Access 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 MongoDB Data Access 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 MongoDB Data Access

1. Log into your MongoDB Data Access account as an administrator.

2. At the top of the sidebar menu, click MongoDB Atlas.

3. In the sidebar menu, navigate to IDENTITY & ACCESS → Federation. The "Federation" page opens.

4. Click Open Federation Management App. The "Federation Management" page opens in a new tab.

5. In the sidebar menu, click Identity Providers. The "Identity Providers" page opens.

6. Click Set Up Identity Provider. The "Configure Identity Provider" page opens.

7. Click the Workforce Identity Federation tile and then click Continue.

8. Under "Select a protocol", click the OIDC for Data Access tile.

9. Under "OIDC Protocol Settings", enter a unique name for your configuration into the Configuration Name field.

10. Enter a brief description of your configuration into the Configuration Description field.

11. Return to the Duo Admin Panel. Under "Metadata", copy the Issuer URL and paste it into the MongoDB Data Access Issuer URI field.

12. Return to the Duo Admin Panel. Copy the Client ID and paste it into the MongoDB Data Access Client ID and Audience fields.

13. In MongoDB Data Access, type openid into the Requested Scopes field.

14. Click Add more scopes and type profile into the empty field.

15. Click Add more scopes and type email into the empty field.

16. Click Group Membership.

17. Make sure groups is shown in the Customize Groups Claim field.

18. Make sure sub is shown in the Customize User Claim field.

19. Click User ID.

20. Delete sub and type email into the Customize User Claim field.

21. Click Save and Finish. You will return to the "Identity Providers" page.

22. Return to the Duo Admin Panel. Under "Relying Party", type https://localhost:27097/redirect into the Sign-In Redirect URLs field.

    

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

24. Return to the MongoDB Data Access "Identity Providers" page. In the sidebar menu, click Organizations. The "Linked Organizations" page opens.

25. On your organization's row, click CONFIGURE ACCESS in the "Actions" column.

26. Under "Identity Provider(s)", click Connect Identity Provider. The "Connect Identity Provider(s)" pop-up window opens.

27. Click the checkbox next to your identity provider and then click Connect.

28. At the top of the sidebar menu, click MongoDB.

29. In the sidebar menu, navigate to IDENTITY & ACCESS → All Projects.

30. In the "Project Name" column, click your project.

31. In the sidebar menu, navigate to SECURITY → Database & Network Access. The "Database Users" page opens.

32. Make sure "Federated Auth" is shown in the "Authentication Method" column and a role is assigned in the "MongoDB Roles" column for your applicable user(s).

Configure MongoDB Compass or MongoDB Shell

You must configure MongoDB Compass or MongoDB Shell before you log on to MongoDB Data Access with SSO. MongoDB Compass is configured through the User Interface (UI), and MongoDB Shell is configured through a Command Line Interface (CLI).

Configure MongoDB Compass

1. Log into your MongoDB Data Access account as an administrator.

2. At the top of the sidebar menu, click MongoDB Atlas.

3. In the sidebar menu, navigate to IDENTITY & ACCESS → All Projects. The "All Projects" page opens.

4. In the "Project Name" column, click your project.

5. Under "Clusters", click Connect. The "Connect to Cluster" pop-up window opens.

6. Under "Access your data through tools", click Compass.

7. Under "Connecting with MongoDB Compass", click I have MongoDB Compass installed.

   Note: If you do not have MongoDB Compass installed, click I don't have MongoDB Compass installed and follow the on-screen instructions.

8. Under "1. Choose your version of Compass", click the drop-down menu and select your applicable version.

9. Under "2. Copy the connection string, then open MongoDB Compass", click the Federated Auth radio button.

10. Under "Use this connection string in your application", copy the connection string.

11. Click Done. The "Connect to Cluster" pop-up window closes.

12. Open MongoDB Compass in a separate window.

13. In the sidebar menu, click Add new connection. The "New Connection" pop-up window opens.

14. Make sure the Edit Connection String toggle switch is ON.

15. Paste the connection string you copied earlier into the URI field.

16. Click Advanced Connection Options to expand the menu.

17. Click the Authentication tab and then click OIDC.

18. Click OIDC Options to expand the menu.

19. Make sure the Consider Target Endpoint Trusted checkbox is not checked.

20. Make sure the following checkboxes are checked:

    • Use ID token instead of Access Token

    • Send a nonce in the Auth Code Request

    • Use Application-Level Proxy Settings

21. Click Save.

Configure MongoDB Shell

1. Log into your MongoDB Data Access account as an administrator.

2. At the top of the sidebar menu, click MongoDB Atlas.

3. In the sidebar menu, navigate to IDENTITY & ACCESS → All Projects. The "All Projects" page opens.

4. In the "Project Name" column, click your project.

5. Under "Clusters", click Connect. The "Connect to Cluster" pop-up window opens.

6. Under "Access your data through tools", click Shell.

7. Click I have the MongoDB Shell installed.

   Note: If you do not have the MongoDB Shell installed, click I don't have the MongoDB Shell installed and follow the on-screen instructions.

8. Under "1. Select your mongo shell version", click the drop-down menu and select your applicable version.

9. Under "2. Run your connection string in your command line", click the Federated Auth radio button.

10. Under "Run your connection string in your command line", copy the connection string.

11. Click Done. The "Connect to Cluster" pop-up window closes.

12. Open your command terminal and paste the connection string you copied earlier on the command line. Do not press ENTER yet.

13. At the end of the connection string, add a space and type --oidcIDTokenAccessToken.

    Example: mongosh "mongodb+srv://cluster0.begqim.mongodb.net/?authSource=%24external&authMechanism=MONGODB-OIDC" --apiVersion 1 --oidcIDTokenAccessToken

14. Make note of the entire connection string on your command line. You will need it later.

15. Press ENTER. You will be redirected to Duo Single Sign-On to test your configuration.

Learn more about MongoDB Data Access SSO at MongoDB Docs.

Using SSO

Log on to MongoDB Data Access by using either MongoDB Compass or MongoDB Shell.

Using SSO with MongoDB Compass

Open MongoDB Compass. In the sidebar menu under CONNECTIONS, hover your cursor over your cluster and click CONNECT to be redirected to Duo Single Sign-On to begin authentication.

Using SSO with MongoDB Shell

Open your command terminal. Enter the connection string you noted earlier onto the command line and press ENTER to be redirected to Duo Single Sign-On to begin authentication.

Active Directory Login

With 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 AD primary password and click or tap Log in to continue.

Enable Duo Passwordless to log in to Duo SSO backed by Active Directory authentication without entering a password in the future.

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 Active Directory or a SAML IdP redirects back to Duo. Complete Duo two-factor authentication when prompted and then you'll return to MongoDB Data Access to complete the login process.

* Universal Prompt experience shown.

MongoDB Data Access 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 MongoDB Data Access 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.

Automated Provisioning

You may be able to create, manage, and delete users and groups in this application automatically from Duo using SCIM 2.0 provisioning. See Automated Provisioning to learn how.

Troubleshooting

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