Browser extension API authentication, without 2FA

[joel72265]

When 2FA is enabled on a vault or organization, every time a user logs in to the browser extension they need to use both a username/password and 2FA.

Suggestions:
a) generate an API key for each vault that the user need to register when they setup the browser extension
b) have the browser extension generate an API key that the vault admin needs to approve to authenticate the browser extension (better management). API key management is already there in the Vaultwarden server. eg. like Syncthing, Linkding uses to authenticate clients

Outcome:
The user can login to the browser extension using just a username/password. But if the user logs in to the webpage/web vault they need to use both a username/password and 2FA . The user cannot login to the browser extension if the API key is not authenticated.

Related posts:
I was only able to find somewhat related posts
#4241

[BlackDex]

Sounds like a lot of client side changes. Which are not part of this repo.

[joel72265]

:( Thanks for the update