Integrate with Bitwarden
Support level: Community
What is Bitwarden?
Bitwarden is a freemium, open-source password management service that helps users store, manage, and share sensitive information securely online.
Preparation
The following placeholders are used in this guide:
authentik.companyis the FQDN of the authentik installation.bitwarden.companyis the FQDN of the Bitwarden installation (if using self-hosted Bitwarden).
This documentation lists only the settings that you need to change from their default values. Be aware that any changes other than those explicitly mentioned in this guide could cause issues accessing your application.
To enable Single Sign-On (SSO) with Bitwarden, an enterprise subscription is required.
Configuration methods
You can configure Bitwarden to use either OIDC or SAML; this guide explains both options.
- Log in with OIDC
- Log in with SAML
authentik configuration
In authentik versions earlier than 2026.5, all Redirect URIs are automatically treated as Authorization type. If you are using one of these older authentik versions, add only the Authorization URL to your Redirect URIs and do not configure a Post Logout URI.
To support the integration of Bitwarden with authentik, you need to create an application/provider pair in authentik.
Create an application and provider in authentik
-
Log in to authentik as an administrator and open the authentik Admin interface.
-
Navigate to Applications > Applications and click New Application to open the application wizard.
- Application: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
- Choose a Provider type: select OAuth2/OpenID Connect as the provider type.
- Configure the Provider: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
- Note the Client ID, Client Secret, and slug values because they will be required later.
- Add the redirect URIs for your Bitwarden deployment:
- For Bitwarden Cloud US:
- Add a Redirect URI of type
StrictAuthorizationashttps://sso.bitwarden.com/oidc-signin. - Add a Redirect URI of type
StrictPost Logoutashttps://sso.bitwarden.com/oidc-signedout.
- Add a Redirect URI of type
- For Bitwarden Cloud EU:
- Add a Redirect URI of type
StrictAuthorizationashttps://sso.bitwarden.eu/oidc-signin. - Add a Redirect URI of type
StrictPost Logoutashttps://sso.bitwarden.eu/oidc-signedout.
- Add a Redirect URI of type
- For self-hosted Bitwarden:
- Add a Redirect URI of type
StrictAuthorizationashttps://bitwarden.company/sso/oidc-signin. - Add a Redirect URI of type
StrictPost Logoutashttps://bitwarden.company/sso/oidc-signedout.
- Add a Redirect URI of type
- For Bitwarden Cloud US:
- Select any available Signing Key.
- Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's Application Dashboard page.
-
Click Submit to save the new application and provider.
Bitwarden configuration
-
Log in to the Bitwarden web app as an administrator. For Bitwarden Cloud EU accounts, select
bitwarden.eufrom the Accessing menu. If you are using self-hosted Bitwarden, log in tohttps://bitwarden.company/#/login. -
Open the Admin Console using the product switcher.
-
In the sidebar, navigate to Settings > Single sign-on, and enter the following settings:
- Allow SSO authentication: Select this option.
- SSO Identifier: enter a globally unique SSO identifier. Members with a matching claimed domain can bypass entering this identifier; domain verification is outside the scope of this guide.
- Type: select OpenID Connect.
- Under OpenID connect configuration:
- Authority:
https://authentik.company/application/o/<application_slug>/ - Client ID:
<Client ID from authentik> - Client Secret:
<Client Secret from authentik> - OIDC Redirect Behavior: select Redirect GET.
- Authority:
-
Click Save.
authentik configuration
To support the integration of Bitwarden with authentik, you need to create an application/provider pair in authentik.
Create an application and provider in authentik
authentik 2026.5 introduces changes to how the SAML provider behaves. Specifically, the provider now automatically sets the Issuer value to: https://authentik.company/application/saml/<application_slug>/metadata/
Older versions of authentik set this value to authentik by default. If you're running an older version, please set Issuer to https://authentik.company/application/saml/<application_slug>/metadata/, where <application_slug> is the slug that you selected for the application.
-
Log in to authentik as an administrator and open the authentik Admin interface.
-
Navigate to Applications > Applications and click New Application to open the application wizard.
- Application: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Note the slug value because it will be required later.
- Choose a Provider type: select SAML Provider as the provider type.
- Configure the Provider: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
- Temporarily set the ACS URL to
https://temp.temp - Under Advanced protocol settings, select any available Signing Certificate.
- Temporarily set the ACS URL to
- Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's Application Dashboard page.
-
Click Submit to save the new application and provider.
Download certificate file
- Log in to authentik as an administrator and open the authentik Admin interface.
- Navigate to Applications > Providers and click on the name of the provider that you created in the previous section (e.g.
Provider for Bitwarden). - Under Related objects > Download signing certificate, click on Download. This downloaded file is your certificate file and it will be required in the next section.
Bitwarden configuration
- Log in to the Bitwarden web app as an administrator. For Bitwarden Cloud EU accounts, select
bitwarden.eufrom the Accessing menu. If you are using self-hosted Bitwarden, log in tohttps://bitwarden.company/#/login. - Open the Admin Console using the product switcher.
- In the sidebar, navigate to Settings > Single sign-on, and enter the following settings:
- Allow SSO authentication: Select this option.
- SSO Identifier: enter a globally unique SSO identifier. Members with a matching claimed domain can bypass entering this identifier; domain verification is outside the scope of this guide.
- Type: select SAML 2.0.
- Under SAML service provider configuration:
- Expect signed assertions: Select this option.
- Under SAML identity provider configuration:
- Entity ID:
https://authentik.company/application/saml/<application_slug>/metadata/ - Single sign-on service URL:
https://authentik.company/application/saml/<application_slug>/ - Single log-out service URL:
https://authentik.company/application/saml/<application_slug>/ - X509 public certificate: Paste the contents of your certificate file, without the
-----BEGIN CERTIFICATE-----and-----END CERTIFICATE-----lines.
- Entity ID:
- Under SAML service provider configuration, note the SP entity ID and Assertion consumer service (ACS) URL values because they will be required in the next section.
- Click Save.
Reconfigure authentik provider
- Log in to authentik as an administrator and open the authentik Admin interface.
- Navigate to Applications > Providers and click the Edit icon of the newly created Bitwarden provider.
- Under Protocol settings, set the following required configurations:
- ACS URL: set to the Assertion consumer service (ACS) URL from Bitwarden.
- Audience: set to the SP entity ID from Bitwarden.
- Click Update.
Configuration verification
To confirm that authentik is properly configured with Bitwarden, log out and open Bitwarden.
Enter the email address of a Bitwarden account and click Use single sign-on. If you haven't claimed the email domain in Bitwarden, enter the unique SSO identifier that you selected, and click Continue. You should be redirected to authentik to log in. After successfully logging in, you should be redirected to the Bitwarden dashboard.
Depending on your Member decryption options setting in Bitwarden, you may still be required to enter your master password after signing in via SSO.