mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-24 17:12:43 -05:00
[GH-ISSUE #6909] Auto-enable 2FA is enabled in settings but does not enforce Email 2FA for new users #19337
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 @tabedzki on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6909
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
v1.35.4
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
tailscale:v1.94.2
Host/Server Operating System
Linux
Operating System Version
macOS
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Expected Result
I expected 2FA to be enabled for new accounts.
Actual Result
Email 2FA was not enabled for new users.
Logs
Screenshots or Videos
Additional Context
No response
@stefan0xC commented on GitHub (Mar 12, 2026):
Users would have to be in an organization with 2FA policy enabled for the
email_2fa_auto_fallbackto have any effect. There is no way to enforce 2FA for all users and it also won't effect Administrators or Owners.9c7df6412c/src/db/models/org_policy.rs (L281-L288)