rhino/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-22 09:49:20 -07:00
Code Issues Packages Projects Releases Wiki Activity

Add the information contained in external issues (can be closed).

Timshel
2026-01-04 21:15:30 +01:00
parent a53d4ddcfe
commit dfea572390
1 changed files with 18 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
Enabling-SSO-support-using-OpenId-Connect.md

@@ -148,9 +148,25 @@ Server configuration should look like:
- `Failed to discover OpenID provider: Failed to parse server response`:
- First ensure that the Authority endpoint with `/.well-known/openid-configuration` appended is reacheable.
- Next check that the document return `id_token_signing_alg_values_supported: ["RS256"]`\
If it returns `HS256` then selecting the default signing key again should fix the issue ([steps](https://github.com/Timshel/vaultwarden/issues/107#issuecomment-3200007338)).
If it returns `HS256` then selecting the default signing key again should fix the issue.\
Steps:
1. Open **Authentik admin panel** > **Providers** > Open your **Vaultwarden provider**
2. Click **Edit** > Change the **Signing key** to any of your keys
- If unsure choose the built-in one from Authentik
3. Click **Update**
4. Retry
- `Failed to contact token endpoint: Parse(Error ... Invalid JSON web token: found 5 parts`: \
This error is probably due to an encrypted token (JWE), ensure that no encryption key is used ([steps](https://github.com/dani-garcia/vaultwarden/issues/6230#issuecomment-3245196399)).
This error is probably due to an encrypted token (JWE), ensure that no encryption key is used.\
Steps:
1. Open **Authentik admin panel** > **Providers** > Open your **Vaultwarden provider**
2. Click **Edit** > Make sure Encryption Key is empty.
3. **If not empty**: Select -------- in the dropdown.
4. Make sure not to touch the **Signing Key**, a valid certificate has to be selected
5. Click **Update**
6. Retry
## Casdoor