mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #6316] Invited Users Not Redirected to SSO Login with SSO_ONLY Mode #2402
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#2402
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 @kaeferpsd on GitHub (Sep 23, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6316
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
1.34.3-a2ad1dc7
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
https://github.com/NginxProxyManager/nginx-proxy-manager?utm_source=nginx-proxy-manager
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Environment
Vaultwarden Version: vaultwarden/server:testing
SSO Provider: Microsoft Azure AD (OpenID Connect)
Configuration: SSO_ONLY mode enabled
Problem Description
When SSO_ONLY: "true" is configured and a new user is invited to an organization, the user is not properly redirected to the SSO login flow. Instead, they are prompted to enter a master password that they never created, creating an impossible authentication loop.
Steps to Reproduce
Configure Vaultwarden with SSO_ONLY mode:
Admin invites a new user via organization invite
New user receives invitation email
User clicks "Accept Invite" link from email
User is presented with login form asking for master password
Expected Result
Expected Behavior
User should be automatically redirected to Microsoft Azure AD SSO login
After successful SSO authentication, user should then be prompted to create their first master password for vault encryption
User should then gain access to the organization
Actual Behavior
User is immediately prompted for master password without SSO redirect
Since user never created a master password, they cannot proceed
No way to access SSO login from this state
Actual Result
Additional Context
Regular SSO login works correctly when users access the main domain directly
The issue appears to be specific to the invitation acceptance flow
Temporarily disabling SSO_ONLY allows users to complete registration, but defeats the purpose of SSO-only mode
This creates a broken user experience where invited users cannot join the organization
Workaround
Currently, the only workaround is to:
Temporarily set SSO_ONLY: "false"
Have user complete initial registration
Re-enable SSO_ONLY: "true"
Expected Fix
The invitation acceptance flow should properly redirect to SSO authentication when SSO_ONLY mode is enabled, rather than presenting the traditional login form.
Logs
Screenshots or Videos
No response
Additional Context
No response
@Timshel commented on GitHub (Oct 21, 2025):
Hey
Sorry I was not around when the PR was opened.
At the moment Org invitation is broken in
testing.I'll check again once it's merged, but it used to work.
SSO_ONLYneed to be activated at the time of the invitation, but I think I will change it for the invitation to redirect to the SSO flow as soon as it's activated (SSO_ENABLED).@Timshel commented on GitHub (Oct 22, 2025):
Hey,
The PR was merged, do you still have the issue ?
@alexanderkraemer commented on GitHub (Jan 6, 2026):
I still experience this issue.
SSO_ONLY and SSO_ENABLED is set to true, but users still are not seeing the SSO option, except when they manually go to
/#/ssopath.Otherwise the standard login form just returns an error, that sso is required for this user.
@stefan0xC commented on GitHub (Jan 8, 2026):
If it's just the login page can you check if your
/css/vaultwarden.cssdoes include.vw-continue-loginand does not include.vw-sso-loginand.vw-email-sso?My suspicion would be that something in your setup might have cached that file indefinitely.
@alexanderkraemer commented on GitHub (Jan 8, 2026):
You are right, the
vaultwarden.cssdoes include.vw-continue-loginand does not contain.vw-sso-loginand.vw-email-ssowell it is running on k8s, so killing the pod should clear the cache....
Not sure why it didn't clear the cache beforehand. i can see i did a deploy of that app.
nvmd, it's working now :)
thanks!