mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Can't use other 2FA method when logging in through browser extension #1625
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 @Karbust on GitHub (Jul 4, 2023).
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: ADMIN_TOKEN
Clients used: As far as I know this issue only happens when logging in through the browser extension.
Reverse proxy and version: nginx/1.25.1
Steps to reproduce
Just a normal docker installation.
Expected behaviour
Ability to choose the 2FA option I want to use.
Actual behaviour
Only allows me to login using WebAuthn, even though I'm on a remote desktop, impossible for me to use the physical authentication key on that machine.
@BlackDex commented on GitHub (Jul 4, 2023):
Have you configured other 2FA options? If not, then it will not show those options.
@Karbust commented on GitHub (Jul 4, 2023):
Yes, I also have Authenticator app enabled, and I can use it logging in directly on the web interface, windows application, ios app and android app, just can't use it when logging in through the chrome extension...
@BlackDex commented on GitHub (Jul 4, 2023):
I'm afraid that is not something we can fix. If you are able to use it on all other clients then Vaultwarden sends the correct response to the clients. It might be that some headers are not correct, or some other extension is blocking the workings of the extension, for example i know Brave browser has some specific extension restrictions which could cause issues.
Try it with a new chrome profile without any extensions installed except the Bitwarden extension and see if that also fails.
If it doesn't then your current browser profile is blocking something, if not, then it might be an extension issue, and that is not something we can fix.