Okta OIDC Implementation
Okta OIDC Implementation
This article contains Okta-specific help for configuring Login with SSO via OpenID Connect (OIDC). For help configuring Login with SSO for another OIDC IdP, or for configuring Okta via SAML 2.0, see OIDC Configuration or Okta SAML Implementation.
Configuration involves working simultaneously within the Bitwarden Web Vault and the Okta Admin Portal. As you proceed, we recommend having both readily available and completing steps in the order they're documentated.
Open SSO in the Web Vault
Navigate to your Organization's Manage → Single Sign-On screen:
You don't need to edit anything on this screen yet, but keep it open for easy reference.
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 Okta App
In the Okta Admin Portal, select Applications → Applications from the navigation. On the Applications screen, select the Create App Integration button. For Sign-on method, select OIDC - OpenID Connect. For Application type, select Web Application:
On the New Web App Integration screen, configure the following fields:
|App integration name||Give the app a Bitwarden-specific name.|
|Grant type||Enable the following grant types:
- Client acting on behalf of itself → Client Credentials
- Client acting on behalf of a user → Authorization Code
|Sign-in redirect URIs||Set this field to your Callback Path, which can be retrieved from the Bitwarden SSO Configuration screen.
For Cloud-hosted customers, this is always
|Sign-out redirect URIs||Set this field to your Signed Out Callback Path, which can be retrieved from the Bitwarden SSO Configuration screen.|
|Assignments||Use this field to designate whether all or only select groups will be able to use Bitwarden Login with SSO.|
Once configured, select the Next button.
Get Client Credentials
On the Application screen, copy the Client ID and Client secret for the newly created Okta app:
You'll need to use both values during a later step.
Get Authorization Server Information
Select Security → API from the navigation. From the Authorization Servers list, select the server you'd like to use for this implementation. On the Settings tab for the server, copy the Issuer and Metadata URI values:
You'll need to use both values during the next step.
Back to the Web Vault
At this point, you've configured everything you need within the context of the Okta Admin Portal. Jump back over to the Bitwarden Web Vault to configure the following fields:
|Authority||Enter the retrieved Issuer URI for your Authorization Server.|
|Client ID||Enter the retrieved Client ID for your Okta app.|
|Client Secret||Enter the retrieved Client secret for your Okta app.|
|Metadata Address||Enter the retrieved Metadata URI for your Authorization Server.|
|OIDC Redirect Behavior||Select Redirect GET. Okta currently does not support Form POST.|
|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 (
|Expected "acr" Claim Value in Response||Define the
When you're done configuring these fields, Save your work.
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:
Enter the configured Organization Identifier and select Log In. If your implementation is successfully configured, you'll be redirected to the Okta login screen:
After you authenticate with your Okta credentials, enter your Bitwarden Master Password to decrypt your Vault!