Two new SCSS rules in src/static/templates/scss/vaultwarden.scss.hbs that hide .vw-email-form-field and .vw-remember-email when sso_only=true.
Why
When SSO_ENABLED=true && SSO_ONLY=true the email entered on the login page is ignored by the backend (single-tenant SSO uses FAKE_SSO_IDENTIFIER), but the page still asks for it and forces the user to type something. Hiding the input simplifies the UX to a single "Continue with SSO" button.
How
Following the existing pattern used for .vw-or-text / .vw-other-login (already conditional on sso_only), this PR adds an analogous block for the email form-field and the Remember-email checkbox.
Depends on
The classes .vw-email-form-field and .vw-remember-email are added by a companion patch in vw_web_builds: view PR. Without that patch the new rules simply do not match anything.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dani-garcia/vaultwarden/pull/7173
**Author:** [@IacopoSb](https://github.com/IacopoSb)
**Created:** 5/1/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `feat/sso_login_graphical_fix`
---
### 📝 Commits (2)
- [`96b81f7`](https://github.com/dani-garcia/vaultwarden/commit/96b81f7287d16e4a26da23676454dde5594f62df) fix: hide email field on login page when SSO_ONLY is enabled
- [`dd4759f`](https://github.com/dani-garcia/vaultwarden/commit/dd4759f717c845aac327f7bc8496e07c9b4c93e0) Merge commit '07aa377a' into feat/sso_login_graphical_fix
### 📊 Changes
**1 file changed** (+10 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `src/static/templates/scss/vaultwarden.scss.hbs` (+10 -0)
</details>
### 📄 Description
Two new SCSS rules in `src/static/templates/scss/vaultwarden.scss.hbs` that hide `.vw-email-form-field` and `.vw-remember-email` when `sso_only=true`.
## Why
When `SSO_ENABLED=true && SSO_ONLY=true` the email entered on the login page is ignored by the backend (single-tenant SSO uses `FAKE_SSO_IDENTIFIER`), but the page still asks for it and forces the user to type something. Hiding the input simplifies the UX to a single "Continue with SSO" button.
## How
Following the existing pattern used for `.vw-or-text` / `.vw-other-login` (already conditional on `sso_only`), this PR adds an analogous block for the email form-field and the Remember-email checkbox.
## Depends on
The classes `.vw-email-form-field` and `.vw-remember-email` are added by a companion patch in vw_web_builds: [view PR](https://github.com/vaultwarden/vw_web_builds/pull/24). Without that patch the new rules simply do not match anything.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/7173
Author: @IacopoSb
Created: 5/1/2026
Status: 🔄 Open
Base:
main← Head:feat/sso_login_graphical_fix📝 Commits (2)
96b81f7fix: hide email field on login page when SSO_ONLY is enableddd4759fMerge commit '07aa377a' into feat/sso_login_graphical_fix📊 Changes
1 file changed (+10 additions, -0 deletions)
View changed files
📝
src/static/templates/scss/vaultwarden.scss.hbs(+10 -0)📄 Description
Two new SCSS rules in
src/static/templates/scss/vaultwarden.scss.hbsthat hide.vw-email-form-fieldand.vw-remember-emailwhensso_only=true.Why
When
SSO_ENABLED=true && SSO_ONLY=truethe email entered on the login page is ignored by the backend (single-tenant SSO usesFAKE_SSO_IDENTIFIER), but the page still asks for it and forces the user to type something. Hiding the input simplifies the UX to a single "Continue with SSO" button.How
Following the existing pattern used for
.vw-or-text/.vw-other-login(already conditional onsso_only), this PR adds an analogous block for the email form-field and the Remember-email checkbox.Depends on
The classes
.vw-email-form-fieldand.vw-remember-emailare added by a companion patch in vw_web_builds: view PR. Without that patch the new rules simply do not match anything.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.