Bitwarden Passkeys No Longer Working

[vik043]

Same issue here… it’s been happening for quite a while.

[eufnis]

Is there a way to disable the necessity of verifying “with an unlock method such as biometrics, PIN, or master password”?

When beginning a browsing session, I will unlock my Bitwarden and want to be able to login to sites without constantly having to enter a PIN/password (no biometrics used). At the close of my session, I will lock my Bitwarden. Therefore it would be great to not have a prompt every time I want to login somewhere.

[grb]

The short answer is that this requirement will temporarily go away in an upcoming release of the browser extension, but because User Verification is required for Bitwarden to be in compliance with the WebAuthn specs, this requirement will return again in the near future (hopefully in the form that is independent of the vault unlock method).

For further discussion of this issue, please review the following recent forum threads:

Passkeys - can you turn off the master password verification for sites?

Can you turn this off for sites where I don’t want to have to enter my master password for secondary verification (in the browser extension) when logging into sites with a passkey stored in my BW vault? Some sites ask for this (such as this forum) but others do not.

Does Bitwarden need to do User Verification anew for each authentication ceremony?

A side discussion arose in the Feature Request thread “Passkey User Verification Independent of Vault Unlock Method”, about whether it is even necessary for Bitwarden to require a new User Verification (UV) each time that a passkey is used for authenticating to a Relying Party (RP) that has specified that UV is required. To avoid diluting the actual feature proposal in that Feature Request thread (to make the UV method separate from the vault unlock method, given that Bitwarden is going to requ…

[bwuser12]

Same here. Why can’t I use Touch ID on my Macbook Air to verify? I have to type in my master password to use Passkey stored in Bitwarden on Chrome now.

[Nail1684]

@bwuser12

Same here. Why can’t I use Touch ID on my Macbook Air to verify? I have to type in my master password to use Passkey stored in Bitwarden on Chrome now.

Did you read the post - and maybe follow the given links by @grb - just above your post?

[grb]

This should be fixed in an upcoming release (probably the July update). In the meantime, you can use a PIN instead of biometrics to unlock your browser extension — then you will only need the PIN instead of the master password to use your stored passkeys.

[eufnis]

I’m not willing to have to type out my PIN every time I want to login to a site, forget about having to input the master password.

I don’t plan to start using passkeys anytime soon due to this requirement.

[grb]

Upgrade your browser extension to 2024.7.0, and then hope for a better UX in Bitwarden’s next implementation of the User Verification requirement. Consider supporting the following feature request:

Passkey User Verification Independent of Vault Unlock Method

Background: As of version 2024.6.0, Bitwarden passkeys now honor requests by Relying Parties to require User Verification. Currently, this results in the user being reprompted for their Bitwarden Master Password (or alternative vault unlock method) any time that they use a passkey for which User Verification is required (see PR 8746). For those who have strong Master Passwords and vault unlock PINs (something that Bitwarden presumably encourages), this new behavior can create significant frict…

[steveremington (Steve Remington (Work))]

When is the Bitwarden browser extension 2024.7.0 available? I just checked the Chrome Web Store, and the current extension version is 2024.6.2.

[DenBesten]

Its release has not yet been announced. This link is a good place to keep an eye on what is coming out.

Lately, the dot-zero releases tend to come out mid-month, and if the particular piece involves a “vendor store”, that tends to add a few days because the various stores have approval processes that kick in after Bitwarden submits the release to them.

[grb]

Github is a more up-to-date source, although the release notes there are not always as descriptive as those in the Help Center.

@DenBesten

Its release has not yet been announced.

Version 2024.7.0 was in fact released (which is why I recommended to upgrade), but as of yesterday, it seems that Bitwarden has pulled the release, reverting to version 2024.6.3/2024.6.4.

Not sure what’s going on — perhaps @cagonzalez can shed some light?