Duo Single Sign-On for Bitwarden

Overview

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 and zero-trust policies.

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 Bitwarden logins. Duo Single Sign-On acts as an identity provider (IdP), authenticating your users using existing on-premises Active Directory (AD) or another SSO IdP. Duo SSO prompts users for two-factor authentication and performs endpoint assessment and verification before permitting access to Bitwarden.

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 Bitwarden. Duo checks the user, device, and network against an application's policy before allowing access to the application.

Configure Single Sign-On

Before configuring Bitwarden with Duo SSO using Security Assertion Markup Language (SAML) 2.0 authentication you'll first need to enable Duo Single Sign-On for your Duo account and configure a working authentication source.

Once you have your SSO authentication source working, continue to the next step of creating the Bitwarden application in Duo.

Create the Bitwarden Application in Duo

1. Log on to the Duo Admin Panel and navigate to Applications.

2. Click Protect an Application and locate the entry for Bitwarden 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 Bitwarden. See Protecting Applications for more information about protecting applications in Duo and additional application options. You'll need the information on the Bitwarden page under Downloads later.

3. Bitwarden 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
   <Email Address>	mail	Email

   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.

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

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

We've already updated the Duo Bitwarden 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 Bitwarden 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.

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.

The "Universal Prompt" area of the application details page shows that this application is "Ready to activate", with these activation control options:

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

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 "Activation 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. However, this will still deliver the Duo prompt via redirect, not in an iframe.

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.

Enable Bitwarden for SSO

1. Log into your Bitwarden account as an administrator.

2. Navigate to the Admin Console.

3. In the left menu sidebar, navigate to Settings → Single Sign On. The "Single Sign On" page opens.

4. Click the Allow SSO authentication checkbox.

5. Enter a unique name into the SSO identifier field.

6. Under "Member decryption options", click the Master password radio button.

7. Click the Type drop-down menu and select SAML 2.0.

8. Under "SAML service provider configuration", copy the SP entity ID and paste it into the Duo Admin Panel SP entity ID field under "Service Provider".

9. Return to the Bitwarden "Single sign-on" page. Copy the Assertion consumer service (ACS) URL and paste it into the Duo Admin Panel Assertion consumer service (ACS) URL field.

10. In the Duo Admin Panel, enter the SSO identifier you created in Bitwarden earlier into the SSO identifier field.

    

11. Return to the Bitwarden "Single sign-on" page. Click the Name ID format drop-down menu and select Persistent.

12. Click the Outbound signing algorithm drop-down menu and select http://www.w3.org/2001/04/xmldsig-more#rsa-sha256.

13. Click the Signing behavior drop-down menu and select If IdP Wants Authn Requests Signed.

14. Click the Minimum incoming signing algorithm drop-down menu and select http://www.w3.org/2001/04/xmldsig-more#rsa-sha256.

15. Make sure the Expect signed assertions and Validate certificates checkboxes are unchecked.

16. Return to the Duo Admin Panel. Under "Metadata", copy the Entity ID and paste it into the Bitwarden Entity ID field under "SAML identity provider configuration".

17. Return to the Duo Admin Panel. Copy the Single sign-on service URL and paste it into the Bitwarden Single sign-on service URL field.

    

18. In the Bitwarden "Single sign-on" page, click the Binding type drop-down menu and select HTTP POST.

19. Delete the text in the Single log-out service URL field.

20. Return to the Duo Admin Panel with the Bitwarden application open. Under "Downloads", click Copy certificate. Return to Bitwarden and paste the copied certificate file text into the Bitwarden X.509 public certificate field, deleting the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines from the pasted certificate text.

21. In the Bitwarden "Single sign-on" page, click the Outbound signing algorithm drop-down menu and select http://www.w3.org/2001/04/xmldsig-more#rsa-sha256.

22. Make sure the Allow outbound logout requests and Sign authentication requests checkboxes are unchecked.

23. Click Save.

24. Return to the Duo Admin Panel. Scroll to the bottom of the page and click Save.

Learn more about Bitwarden SSO at the Bitwarden Help Center.

Using SSO

You can log on to Bitwarden by navigating to your Bitwarden SSO page e.g., https://vault.bitwarden.com/#/sso. Enter your SSO identifier into the SSO identifier field and click Log in 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 Bitwarden to complete the login process.

* Universal Prompt experience shown.

You can also log into Bitwarden using Duo Central, our cloud-hosted portal which allows users to access all of their applications in one spot. Link to Bitwarden in Duo Central by adding it as an application tile. Once the tile has been added, log into Duo Central and click the tile for IdP-initiated authentication to Bitwarden.

Congratulations! Your Bitwarden 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.

Enable Remembered Devices

To minimize additional Duo two-factor prompts when switching between Bitwarden 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.