PersonalBusinessDownloadPricingHelpBlogContact
Get Started
Log In
PersonalBusinessDownloadPricingHelpBlogContactBusiness SalesGet StartedLog In

Azure OIDC Implementation

This article contains Azure-specific help for configuring Login with SSO via OpenID Connect (OIDC). For help configuring Login with SSO for another OIDC IdP, or for configuring Azure via SAML 2.0, see OIDC Configuration or Azure SAML Implementation.

Configuration involves working simultaneously within the Bitwarden web vault and the Azure Portal. As you proceed, we recommend having both readily available and completing steps in the order they are documented.

Open SSO in the web vault

If you are coming straight from OIDC Configuration, you should already have an organization ID created. If you don't refer to that article to create an organization ID for SSO.

Navigate to your organization's ManageSingle Sign-On screen:

OIDC Configuration
OIDC Configuration

You don't need to edit anything on this screen yet, but keep it open for easy reference.

tip

If you're self-hosting Bitwarden, you can use alternative Member Decryption Options. This feature is disabled by default, so continue with Master Password decryption for now and learn how to get started using Key Connector once your configuration is complete and successfully working.

Create an app registration

In the Azure Portal, navigate to App registrations and select the New registration button:

Create App Registration
Create App Registration

On the Register an application screen, give your app a Bitwarden-specific name and specify which accounts should be able to use the application. This selection will determine which users can use Bitwarden login with SSO.

Register a redirect URI

Select Authentication from the navigation and select the Add a platform button:

Register a Redirect URI
Register a Redirect URI

Select the Web option on the Configure platforms screen and enter your Callback Path in the Redirect URIs input.

note

Callback Path can be retrieved from the Bitwarden SSO Configuration screen. For cloud-hosted customers, this is always https://sso.bitwarden.com/oidc-signin. For self-hosted instances, this is determined by your configured server URL, for example https://your.domain.com/sso/oidc-signin.

Create a client secret

Select Certificates & secrets from the navigation, and select the New client secret button:

Create Client Secret
Create Client Secret

Give the certificate a Bitwarden-specific name, and choose an expiration timeframe.

Back to the web vault

At this point, you have configured everything you need within the context of the Azure Portal. Return to the Bitwarden web vault to configure the following fields:

Field Description
Authority Enter https://login.microsoft.com/<TENANT_ID>/v2.0, where TENANT_ID is the Directory (tenant) ID value retrieved from the app registration's Overview screen.
Client ID Enter the App registration's Application (client) ID, which can be retrieved from the Overview screen.
Client Secret Enter the Secret Value of the created client secret.
Metadata Address For Azure implementations as documented, you can leave this field blank.
OIDC Redirect Behavior Select either Form POST or Redirect GET.
Get Claims From User Info Endpoint Enable this option if you receive URL too long errors (HTTP 414), truncated URLS, and/or failures during SSO.
Additional/Custom Scopes Define custom scopes to be added to the request (comma-delimited).
Additional/Custom User ID Claim Types Define custom claim type keys for user identification (comma-delimited). When defined, custom claim types are searched for before falling back on standard types.
Additional/Custom Email Claim Types Define custom claim type keys for users' email addresses (comma-delimited). When defined, custom claim types are searched for before falling back on standard types.
Additional/Custom Name Claim Types Define custom claim type keys for users' full names or display names (comma-delimited). When defined, custom claim types are searched for before falling back on standard types.
Requested Authentication Context Class Reference values Define Authentication Context Class Reference identifiers (acr_values) (space-delimited). List acr_values in preference-order.
Expected "acr" Claim Value in Response Define the acr Claim Value for Bitwarden to expect and validate in the response.

When you are done configuring these fields, Save your work.

tip

You can require users to log in with SSO by activating the single sign-on authentication policy. Please note, this will require activating the single organization policy as well. Learn more.

Test the configuration

Once your configuration is complete, test it by navigating to https://vault.bitwarden.com and selecting the Enterprise Single Sign-On button:

Enterprise Single Sign-On button
Enterprise Single Sign-On button

Enter the configured organization identifier and select Log In. If your implementation is successfully configured, you will be redirected to the Microsoft login screen:

Azure login screen
Azure login screen

After you authenticate with your Azure credentials, enter your Bitwarden master password to decrypt your vault!


Language

Products

Resources

  • Resource Center
  • Community Forums
  • Security Compliance
  • Success Stories
  • User Reviews
  • Newsfeed
  • Subscribe to Updates
©2022 Bitwarden, Inc.
Terms Privacy Sitemap