-
Notifications
You must be signed in to change notification settings - Fork 849
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All lesser known browsers can't use passkeys #4620
Comments
Thank you for your report! We've added this to our internal board for review. |
Thanks @androidacy-user, we are aware of this and we maintain a community list to allow lesser known but vetted browsers: https://github.com/bitwarden/android/blob/main/app/src/main/assets/fido2_privileged_community.json Once you make a PR, adding a browser there, it would be included in the next release. We are however looking into improving this even further, is that something you would be interested in? |
If you list them, I can get them added. |
then why is a browser in that list not working (quetta)? do you genuinely think it's reasonable for user(s) to have to validate against a list (that is linked nowhere in the app!) before they switch browsers? or do you think it's pretty reasonable to have my password manager (that I use to make my life easier, not harder) to at least allow me to "trust" a browser, so that my logins "just work", instead? (not even going to mention non whitelisted browsers aren't even detected as browsers, and bitwarden tries to fill logins for the app instead of the website). idk what the perfect solution is but this is not it |
most likely an update with that commit hasn't come out yet |
Steps To Reproduce
Expected Result
Passkeys work, regardless of Google's or your blessing of the browser.
Actual Result
"Passkey operation failed because browser isn't privileged"
Screenshots or Videos
No response
Additional Context
I shouldn't have to double check if my password manager supports X feature in Y browser before using it. Almost every browser is chromium based, with a handful being Firefox based, so there's no real reason for random browsers to be unable to use passkeys (which wholeheartedly defeats the purpose of having passkeys in the first place!)
Build Version
version 2025.1.0 com.x8bit.bitwarden
What server are you connecting to?
N/A
Self-host Server Version
No response
Environment Details
Pixel running android 15, issue reproducible on any non major browser (i.e., anything besides edge, chrome, Firefox, brave, etc that is either newer or has a smaller user base)
Issue Tracking Info
The text was updated successfully, but these errors were encountered: