mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #6179] SSO login/registration kinda buged from yesterday to today #2362
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2362
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Joly0 on GitHub (Aug 12, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6179
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, ADMIN_TOKEN
Config:
Vaultwarden Build Version
1.34.3-8e7eeab2
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
traefik 3.5
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Web Vault
Client Version
No response
Steps To Reproduce
So this is a weird one. I opened this discussion yesterday https://github.com/dani-garcia/vaultwarden/discussions/6171 after setting up vaultwarden with SSO. In the end i was able to login but only through the desktop application, there was no sso button on the webui or anything, just the plain login with master password or register option.
In the meantime i didnt change any settings, they remained as is and i left it. Today a colleague of mine wanted to try it out and was wondering about an issue when signign in:
I told him he needed to register first, but noticed, that there was no register button anymore. Just an sso login button and the continue button. So he cannot create an account. But atleast now using the sso login button i can login to the web vault.
Reading through the docs i noticed this part https://github.com/dani-garcia/vaultwarden/wiki/Enabling-SSO-support-using-OpenId-Connect#on-sso_allow_unknown_email_verification and tried to figure out what was missing, but from my knowledge entra id, the provider we use, provied the email_verified claim. So i assume i have to add it "Authorization request scopes" or the "Authorization request extra parameters" settings? Not sure though. Also i couldnt find any option (in the admin dashboard) that show the option "SSO_ALLOW_UNKNOWN_EMAIL_VERIFICATION" to disable it.
So i am completely lost now what is going on. Where the register button is, why i couldnt login yesterday but can today, what the error message for my colleague means and why out of the sudden the sso login button appeared in the webui.
Expected Result
At this point, idk what i should expect
Actual Result
I have legit no idea if this is how it should work, why it suddenly does what it does, but the result is, currently only myself can login, others cant register
Logs
Screenshots or Videos
No response
Additional Context
No response
@ArcticLampyrid commented on GitHub (Aug 16, 2025):
I believe this is a environment variable.
@Gauss23 commented on GitHub (Aug 25, 2025):
Maybe the env part from Authentik's manual helps and can be adopted to your Entra IdP:
https://integrations.goauthentik.io/security/vaultwarden/#vaultwarden-configuration
it says:
@Timshel commented on GitHub (Aug 26, 2025):
Hey
The setting should be visible once https://github.com/dani-garcia/vaultwarden/pull/6235 is merged.
In the meantime as mentioned you can set
SSO_ALLOW_UNKNOWN_EMAIL_VERIFICATION=trueas an env variable to ignore the fact that your provider do not sent the email status.And you probably then want to disable
SSO_SIGNUPS_MATCH_EMAIL=false, more details here.@Joly0 commented on GitHub (Sep 1, 2025):
Something still borked somewhere. So i changed both settings:
He goes to the vaultwarden login page, clicks on "Use single sign-on", is redirected to microsoft login screen, then redirected to the login page of vaultwarden with this warning. I can see in the admin page on the users tab, that the user was created, but without an SSO identifier:
@Timshel commented on GitHub (Sep 1, 2025):
The error message is consistent with setting
SSO_SIGNUPS_MATCH_EMAIL=falseand the user already existing.I'm guessing the user was created in a previous attempt which did not complete due to an error.
Searching in the logs around the account creation time should give more information.
For the username the
preferred_usernamereturned by your provider is used, if missing it fallback to the email.@Joly0 commented on GitHub (Sep 1, 2025):
Ok, i hope i havent left any sensitive data in it, but here are the logs:
prior to this, i deleted the problematic user from vaultwarden.
@Timshel commented on GitHub (Sep 1, 2025):
No idea what could be happening:
Initial login return 200, so the identifier should be saved in the
sso_usertable.After this the only way to delete the entry should be via the admin endpoint (a call to
/users/<user_id>/ssowould be visible).But later it can't be found again :(.
Edit: was able to reproduce will look at it.