mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #6277] SSO Button Not Displayed in Web UI Across Multiple Systems and Versions #2390
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#2390
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 @vandita36 on GitHub (Sep 8, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6277
Prerequisites
Vaultwarden Support String
SSO button not showing
Vaultwarden Build Version
tried all latest, testing and downgrading versions
Deployment method
Official Container Image
Custom deployment method
I am unable to see the Single Sign-On (SSO) button in the Vaultwarden web interface. This issue occurs across multiple platforms and versions I have tested:
Windows 10/11
macOS (local Mac Mini)
Ubuntu (local VM and EC2 instance)
I have tested:
Latest stable releases
Older stable releases
Development/testing Docker images
Despite verifying my SSO configuration (Keycloak/Entra ID/Authentik, etc.) and clearing browser cache, the SSO button does not appear. The login works fine through browser extensions and mobile apps, but the web UI remains without the SSO option.
Steps to Reproduce:
Install or update Vaultwarden to any version (stable, old stable, or testing image).
Configure SSO via your provider (Keycloak, Entra ID, etc.).
Access the Vaultwarden web interface.
Observe that the "Use Single Sign-On" button is missing.
Expected Behavior:
The web UI should display the SSO login button when SSO is configured correctly.
Actual Behavior:
The SSO button is not visible in the web interface, despite SSO being functional in other clients (browser extension, mobile app).
Environment:
Vaultwarden versions tested: All stable versions and testing/development images
Deployment method: Docker / Manual installation / Other
Browser: latest
Operating systems tested: Windows, macOS, Ubuntu, EC2 Ubuntu
Additional Notes:
I have tried clearing cache and accessing via multiple browsers.
Other users have reported that SSO works on some versions and setups, indicating this may be environment-specific or a UI bug.
both UI is loading and working just not showing the SSO button.
Reverse Proxy
not using now
Host/Server Operating System
Other
Operating System Version
all sytems I have tried
Clients
Desktop
Client Version
No response
Steps To Reproduce
did SSO button testing
Expected Result
want SSO button on vaultwarden
Actual Result
not showing SSO button
Logs
Screenshots or Videos
No response
Additional Context
No response
@stefan0xC commented on GitHub (Sep 8, 2025):
It's only available in
testingand you also have to enable SSO for the button to be displayed.@nwin commented on GitHub (Sep 10, 2025):
I have the same issue.
SSO_ENABLED=true SSO_ONLY=trueAfter opening the page I get the following screen:


And entering the mail and master password (I get not redirected or anything just prompted to enter, this is a fresh installation with no user setup) it is confirmed that SSO_ONLY works...
@BlackDex commented on GitHub (Sep 10, 2025):
Try to clear your cache, or use an InCognito/Private Browser Window. Bitwarden clients cache some settings, which could cause strange issues like this.
@stefan0xC commented on GitHub (Sep 10, 2025):
Your browser might have an old version of
/css/vaultwarden.cssstill cached. Can you fully reload the web-vault and check again? If it does not change anything please post the support string that you can generate via the/admin/diagnosticspage (after enabling it).@nwin commented on GitHub (Sep 10, 2025):
This did do the trick for me, thanks.