Signed-off-by: Amir Zarrinkafsh <3339418+nightah@users.noreply.github.com>
4.0 KiB
title, description, summary, date, draft, images, weight, toc, aliases, support, seo
| title | description | summary | date | draft | images | weight | toc | aliases | support | seo | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Bitwarden | Integrating Bitwarden with the Authelia OpenID Connect 1.0 Provider. | 2025-04-26T18:35:57+10:00 | false | 620 | true |
|
|
Tested Versions
{{% oidc-common %}}
Assumptions
This example makes the following assumptions:
- Application Root URL:
https://bitwarden.{{< sitevar name="domain" nojs="example.com" >}}/ - Authelia Root URL:
https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/ - Client ID:
bitwarden - Client Secret:
insecure_secret
{{< callout context="tip" title="Did you know?" icon="outline/rocket" >}}
This setup assumes you're using the self-hosted version of Bitwarden. If you're using the SaaS version the redirect_uris are either
usually https://sso.bitwarden.com/oidc-signin or if you're in the EU https://sso.bitwarden.eu/oidc-signin.
{{< /callout >}}
Some of the values presented in this guide can automatically be replaced with documentation variables.
{{< sitevar-preferences >}}
Configuration
Authelia
The following YAML configuration is an example Authelia client configuration for use with Bitwarden which will operate with the application example:
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
- client_id: 'bitwarden'
client_name: 'Bitwarden'
public: false
authorization_policy: 'two_factor'
require_pkce: true
pkce_challenge_method: 'S256'
redirect_uris:
- 'https://bitwarden.{{< sitevar name="domain" nojs="example.com" >}}/oidc-signin'
scopes:
- 'openid'
- 'email'
- 'profile'
response_modes:
- 'form_post'
response_types:
- 'code'
grant_types:
- 'authorization_code'
access_token_signed_response_alg: 'none'
userinfo_signed_response_alg: 'none'
token_endpoint_auth_method: 'client_secret_post'
Application
To configure Bitwarden there is one method, using the Web GUI.
Web GUI
To configure Bitwarden to utilize Authelia as an OpenID Connect 1.0 Provider, use the following instructions:
- Login to your Bitwarden administrator account.
- Select
Admin Console. - Select
Settings. - Select
Single sign-on. - Select
Allow SSO authentication. - If you're using Bitwarden SaaS configure the SSO Identifier per their instructions.
- Select
OpenID Connectfor the type. - Enter the following values:
- Authority:
https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}} - Client ID:
bitwarden - Client Secret:
insecure_secret - Metadata Address:
https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/.well-known/openid-configuration - OIDC redirect behavior:
Form POST - Get claims from user info endpoint: Enabled
- Click Save.