mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-22 16:14:20 -05:00
[PR #6949] [CLOSED] feat: SSO improvements — auto-redirect, Key Connector, logout redirect, auto-enrollment #22073
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?
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/6949
Author: @brendan-kite
Created: 3/16/2026
Status: ❌ Closed
Base:
main← Head:sso-improvements📝 Commits (1)
6fc40c0feat: SSO improvements — auto-redirect, Key Connector, logout redirect, auto-enrollment📊 Changes
7 files changed (+673 additions, -15 deletions)
View changed files
📝
src/api/core/accounts.rs(+139 -2)📝
src/api/identity.rs(+77 -2)📝
src/api/web.rs(+162 -2)📝
src/config.rs(+29 -0)📝
src/crypto.rs(+253 -0)📝
src/db/models/organization.rs(+12 -8)📝
src/db/models/user.rs(+1 -1)📄 Description
Summary
Five new opt-in configuration flags that address long-standing SSO usability gaps:
SSO_AUTO_REDIRECT— Skip the login form entirely, go straight to the IdP (#6191)SSO_LOGOUT_REDIRECT— End the IdP session on logout, preventing auto-re-login loopsSSO_KEY_CONNECTOR— Built-in Key Connector so SSO users never need a master password (#2583)SSO_AUTO_ENROLL— Auto-create org and enroll users on first SSO loginSSO_IDENTIFIER— Custom org identifier for the above featuresAll features are off by default and fully backwards-compatible. 547 lines added across 7 files.
Motivation
With
SSO_ONLY=true, several flows are broken or frustrating:SSO_AUTO_REDIRECTeliminates thisSSO_LOGOUT_REDIRECTfixes this with OIDC RP-Initiated LogoutSSO_KEY_CONNECTORprovides a clean-room, file-based Key ConnectorSSO_AUTO_ENROLLcreates one automaticallySecurity Note
Key Connector stores wrapped master keys server-side, trading the zero-knowledge property for usability. This is the same tradeoff as Bitwarden's official Key Connector. The feature is opt-in and clearly documented.
Configuration
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.