mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-07-16 17:02:14 -05:00
[GH-ISSUE #7150] SSO: Missing the required MasterPasswordUnlock data property on Bitwarden Android client #35579
Reference in New Issue
Block a user
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 @axyn45 on GitHub (Apr 28, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7150
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
v1.35.8
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx 1.28.2
Host/Server Operating System
Linux
Operating System Version
Fedora Server 43
Clients
Android
Client Version
2026.4.0
Steps To Reproduce
Expected Result
User automatically got enrolled and registered
Actual Result
An error pops up with logs to copy. But if you now go back to the login screen and try again to login with SSO+master password or simply master password, user will be logged in.
Logs
Screenshots or Videos
No response
Additional Context
No response
@axyn45 commented on GitHub (Apr 28, 2026):
This issue is similar to #6756 but in my case I didn't encounter the problem for unlocking. This error only appears when trying to log in with SSO and the user is new/not registered in vaultwarden, on Bitwarden Android app (not sure for iOS).
BTW I tried on Windows client as well and it worked with no errors, the registration process was smooth. On the Chrome extension however, after being redirected from SSO auth provider, the page stuck in the loading screen seemingly forever.
@BlackDex commented on GitHub (Apr 28, 2026):
Could you provide the Vaultwarden logs during this attempt?
And if possible z maybe with
LOG_LEVEL=debug@axyn45 commented on GitHub (Apr 28, 2026):
Click to expand
Hope it helps, but I think it's more about the client side. I didn't notice any errors on the server. This issue has bothered me for couple of versions so far. Is it possible that vaultwarden is not responding with complete fields like mobile client expected?
@BlackDex commented on GitHub (Apr 30, 2026):
Looks like i receive the same error if i use an older Bitwarden Self-Hosted.
I think i know what to do to fix this though, but i have to look it upScratch that. Looking at the code it doesn't look like the server side can do anything to resolve this.
As this is not something we can fix on our side I'm going to move this to discussions.