How is Vaultwarden deployed? As a Deployment or Statefulset?
And how many replica's, is the RSA key stored persistent?
Also, the logs of either the Browser, Vaultwarden or IdP should probably provide something useful, try setting the LOG_LEVEL of Vaultwarden to DEBUG and see if you get more details.
<!-- gh-comment-id:4296335248 -->
@BlackDex commented on GitHub (Apr 22, 2026):
How is Vaultwarden deployed? As a Deployment or Statefulset?
And how many replica's, is the RSA key stored persistent?
Also, the logs of either the Browser, Vaultwarden or IdP should probably provide something useful, try setting the `LOG_LEVEL` of Vaultwarden to `DEBUG` and see if you get more details.
I'm having the same issue, I'm also on pretty much the same setup.
when I try to sign up with SSO I get an unexpected Error, but the user is created in vaultwarden.
[2026-04-22 15:26:01.516][vaultwarden::api::identity][ERROR] Unable to refresh login credentials: Access token is close to expiration but we have no refresh token
[2026-04-22 15:26:01.517][response][INFO] (login) POST /identity/connect/token => 401 Unauthorized
In my IdP it seems everything worked and I get a Application authorized.
<!-- gh-comment-id:4296635599 -->
@TuotHash commented on GitHub (Apr 22, 2026):
I'm having the same issue, I'm also on pretty much the same setup.
when I try to sign up with SSO I get an unexpected Error, but the user is created in vaultwarden.
[2026-04-22 15:26:01.516][vaultwarden::api::identity][ERROR] Unable to refresh login credentials: Access token is close to expiration but we have no refresh token
[2026-04-22 15:26:01.517][response][INFO] (login) POST /identity/connect/token => 401 Unauthorized
In my IdP it seems everything worked and I get a Application authorized.
besides that I also think that also the sections about session handling could probably be improved as well (on the documentation page) given that this seems to be an recurring theme in user reported issues that seem to misunderstand how that works and what can be done about it (e.g. what the Bitwarden clients expect, how to adjust the token lifetime lengths and when to turn it off) because at the moment this info is a bit all over the documentation page and I'm not sure what is relevant in general and what is specific for a given identity provider...
<!-- gh-comment-id:4296894311 -->
@stefan0xC commented on GitHub (Apr 22, 2026):
Given the configured `SSO_SCOPES` you probably did not follow the documentation: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-SSO-support-using-OpenId-Connect#microsoft-entra-id
besides that I also think that also the sections about session handling could probably be improved as well (on the documentation page) given that this seems to be an recurring theme in user reported issues that seem to misunderstand how that works and what can be done about it (e.g. what the Bitwarden clients expect, how to adjust the token lifetime lengths and when to turn it off) because at the moment this info is a bit all over the documentation page and I'm not sure what is relevant in general and what is specific for a given identity provider...
Oh I did, but I didn‘t notice the sections further down.
Now I get this Error tho, but I'm unsure what to do. Why is beeing in the org required to log in?
[auth][ERROR] Unauthorized Error: The current user isn't member of the organization
[vaultwarden::api::core::organizations::_][WARN] Request guard OrgMemberHeaders failed: "The current user isn't member of the organization".
[auth][ERROR] Unauthorized Error: The current user isn't member of the organization
[response][INFO] (get_master_password_policy) GET /api/organizations/<org_id>/policies/master-password => 401 Unauthorized
<!-- gh-comment-id:4297093799 -->
@TuotHash commented on GitHub (Apr 22, 2026):
> Given the configured `SSO_SCOPES` you probably did not follow the documentation: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-SSO-support-using-OpenId-Connect#microsoft-entra-id
Oh I did, but I didn‘t notice the sections further down.
Now I get this Error tho, but I'm unsure what to do. Why is beeing in the org required to log in?
[auth][ERROR] Unauthorized Error: The current user isn't member of the organization
[vaultwarden::api::core::organizations::_][WARN] Request guard `OrgMemberHeaders` failed: "The current user isn't member of the organization".
[auth][ERROR] Unauthorized Error: The current user isn't member of the organization
[response][INFO] (get_master_password_policy) GET /api/organizations/<org_id>/policies/master-password => 401 Unauthorized
<!-- gh-comment-id:4297334496 -->
@Timshel commented on GitHub (Apr 22, 2026):
> "Access token is close to expiration but we have no refresh token"
Is usually a sign that the provider require the `offline_access` scope. But for entra additional configuration need to be done on the provider side.
@stefan0xC for session handling there is some [documentation](https://github.com/dani-garcia/vaultwarden/wiki/Enabling-SSO-support-using-OpenId-Connect#session-lifetime), but I agree it's not the most discoverable.
@TuotHash I believe you are now hitting https://github.com/dani-garcia/vaultwarden/issues/7086 which is fixed in `testing`.
Damn I hope it's that, dunno what to do else, but I just updated from .4 to .7 today ;(
<!-- gh-comment-id:4297411634 -->
@TuotHash commented on GitHub (Apr 22, 2026):
Damn I hope it's that, dunno what to do else, but I just updated from .4 to .7 today ;(
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @uka001 on GitHub (Apr 22, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7123
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
V1.35.7
Deployment method
Official Container Image
Custom deployment method
It is deployed in kubernetes. Using gitlab as SOT and ArgoCD.
Reverse Proxy
no
Host/Server Operating System
Linux
Operating System Version
No response
Clients
CLI, Web Vault
Client Version
Firefox v2026.2.0
Steps To Reproduce
Expected Result
Successful login using SSO.
Actual Result
A loop whereby the user is redirected to the login screen after finishing the MFA (microsoft authenticator)
Logs
Screenshots or Videos
No response
Additional Context
No response
@BlackDex commented on GitHub (Apr 22, 2026):
How is Vaultwarden deployed? As a Deployment or Statefulset?
And how many replica's, is the RSA key stored persistent?
Also, the logs of either the Browser, Vaultwarden or IdP should probably provide something useful, try setting the
LOG_LEVELof Vaultwarden toDEBUGand see if you get more details.@TuotHash commented on GitHub (Apr 22, 2026):
I'm having the same issue, I'm also on pretty much the same setup.
when I try to sign up with SSO I get an unexpected Error, but the user is created in vaultwarden.
[2026-04-22 15:26:01.516][vaultwarden::api::identity][ERROR] Unable to refresh login credentials: Access token is close to expiration but we have no refresh token
[2026-04-22 15:26:01.517][response][INFO] (login) POST /identity/connect/token => 401 Unauthorized
In my IdP it seems everything worked and I get a Application authorized.
@BlackDex commented on GitHub (Apr 22, 2026):
@Timshel any quick clues maybe?
@stefan0xC commented on GitHub (Apr 22, 2026):
Given the configured
SSO_SCOPESyou probably did not follow the documentation: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-SSO-support-using-OpenId-Connect#microsoft-entra-idbesides that I also think that also the sections about session handling could probably be improved as well (on the documentation page) given that this seems to be an recurring theme in user reported issues that seem to misunderstand how that works and what can be done about it (e.g. what the Bitwarden clients expect, how to adjust the token lifetime lengths and when to turn it off) because at the moment this info is a bit all over the documentation page and I'm not sure what is relevant in general and what is specific for a given identity provider...
@TuotHash commented on GitHub (Apr 22, 2026):
Oh I did, but I didn‘t notice the sections further down.
Now I get this Error tho, but I'm unsure what to do. Why is beeing in the org required to log in?
[auth][ERROR] Unauthorized Error: The current user isn't member of the organization
[vaultwarden::api::core::organizations::_][WARN] Request guard
OrgMemberHeadersfailed: "The current user isn't member of the organization".[auth][ERROR] Unauthorized Error: The current user isn't member of the organization
[response][INFO] (get_master_password_policy) GET /api/organizations/<org_id>/policies/master-password => 401 Unauthorized
@Timshel commented on GitHub (Apr 22, 2026):
Is usually a sign that the provider require the
offline_accessscope. But for entra additional configuration need to be done on the provider side.@stefan0xC for session handling there is some documentation, but I agree it's not the most discoverable.
@TuotHash I believe you are now hitting https://github.com/dani-garcia/vaultwarden/issues/7086 which is fixed in
testing.@TuotHash commented on GitHub (Apr 22, 2026):
Damn I hope it's that, dunno what to do else, but I just updated from .4 to .7 today ;(