mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
2FA is enabled, but ignored #1688
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 @liashukvladyslav on GitHub (Sep 6, 2023).
Subject of the issue
Within organization, a policy to require two-step login is enabled.
Users have their 2FA configured - they were created before policy enabled, then they have attached 2FA, and only then policy was enabled.
Yet for no obvious reason, 2FA prompt does not occur at user's login, so they are granted access as is.
Deployment environment
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, ADMIN_TOKEN
Steps to reproduce
Expected behaviour
Users that hadn't set 2FA, are kicked from organization with email notification.
Users that set 2FA, are asked for it upon next sign in.
Actual behaviour
Users that hadn't set 2FA are kicked from organization with email notification.
Users that set 2FA, are NOT asked for it upon next sign in.
@BlackDex commented on GitHub (Sep 6, 2023):
If I'm correct users are removed currently if they do not have any MFA/2FA enabled.
Users who have it enabled but checked the
remember this deviceare not going to be asked again after this policy has been enabled. But since they have 2FA enabled, they can have access.Also, members who have an admin or owner access level are not enforced to this policy.
If you would check the Member overview, you probably see that all members of manager or lower access have 2FA enabled, and have a lock symbol.