Another paid subscriber here - I’ve disabled the plugin for now, but wanted to make time to come to the communitiy and vent about how pissed off I am that you broke my stuff without asking me, and without giving me a way to fix it other than swapping to another password manager.
@captainmish Welcome to the forum!
I assume that you are just venting about old frustrations from problems that you experienced in the first week of November, because the kind of issues you are describing were fixed 3 weeks ago.
Thanks @grb - no, not fixed for me. Also, my definition of fixed is “Able to disable passkey functionality in the plugin so that stuff that used to work continues to work”. Today I tried to log in to an old aws account, and could not use my hardware key which was set up already because bitwarded kept intercepting. Clicking “use browser” just resulted in an error. I’ll try later in another one, but I really dont think i should have to - “Hey we’ve got a new feature that intercepts passkey requests, would you like to enable it now?” Would have been more thoughtful I think.
@captainmish Is your browser extension updated to version 2023.10.2?
If so, when your browser extension is either unlocked or completely logged out, Bitwarden should not be prompting you for anything (unless you actually have a passkey stored in Bitwarden for the site that you’re on). If you have any accounts that you need to log into using a hardware passkey while your Bitwarden browser extension is locked, then you can suppress the Bitwarden prompt by adding the full domain name (including base domain and subdomains) for the corresponding login page to the exclusion list under Settings > Excluded Domains.
Thanks, will this just prevent it from interfering with passkeys or will it also prevent password filling?
This will just prevent the passkey prompt from showing up. It will also prevent Bitwarden from asking whether you want to save/update a new password submitted on that website. Auto-filling will not be affected.
The setting to disable the feature globally is available in our upcoming release in December.
Hell its about time
Now if Microsoft would only let us disable the “Sign in with your passkey prompt” in Windows…
FIDO2 envisions 1) device-bound passkeys 2) syncable passkeys: 1) for max security, and 2) for passkey adoption everywhere. 2) are usually platform-managed or PWM managed. You don’t want to get locked into an ecosystem? It’s going to be PWM managed.
The requested feature was released in version 2023.12.0, so I am closing the thread to release the votes.