Not prompted for passkey

[aarongoldenthal]

Describe the bug

After registering a new passkey, I logged out and tried to log back in, but I don't get prompted to use a passkey.

To Reproduce
Steps to reproduce the behavior:

1. Go to Edit profile
2. Click on Register a passkey. The Bitwarden extension prompted me to save the passkey, then I was prompted for a name for the passkey, then it shows as registered in my profile.
3. Log out of site
4. Click Sign in and I'm presented with the normal login screen, but not prompted for a passkey. Tried just clicking Sign in and get the "Try another email address or password" message.

I was able to login fine with login/password.

Expected behavior
Able to log in with passkey.

Screenshots
Chrome showed no console messages. Firefox had the same behavior, but with the following errors (not sure if that's related, I only use Firefox for testing/troubleshooting, although the rest of the site seemed to work fine):

Desktop (please complete the following information):

• OS: Win 11 24H2
• Browser [e.g. chrome, safari]: Chrome 141, Firefox 143

[miharekar]

Interesting! I tried with Safari on iOS, Arc on macOS, Chromium on Arch all worked with native and 1Password. I'm trying to get Bitwarden working in Chromium but it's throwing errors and doesn't want to even persist the passkey 🤔

I don't have access to a Windows machine, but I'll try to make Bitwarden work for me to see if I experience the same on login.

As for Firefox errors - that looks like an extension or something else in your network stack blocking and/or malforming JavaScript files. But it's very strange because none of those file names match anything from visualizer.coffee source and/or import maps.

[aarongoldenthal]

As for Firefox errors - that looks like an extension or something else in your network stack blocking and/or malforming JavaScript files. But it's very strange because none of those file names match anything from visualizer.coffee source and/or import maps.

Very possible, I run an ad blocker and DNS sinkhole.

[miharekar]

I see the same errors in Zen and they seem to originate from https lib which is required by appsignal lib for monitoring errors. Oh, the irony 😂

As for Bitwarden - I got it to persist the passkey, but it's never completing the await navigator.credentials.get({ publicKey, mediation: "conditional" }) request. I even tried adding a button and have an explicit mediation, but the result was the same.

Apparently passkeys still aren't as reliable as they would have us believe 😅

I'll try some more things in the following days, but if you (or anyone else) have any ideas: please let me know!

[aarongoldenthal]

Apparently passkeys still aren't as reliable as they would have us believe 😅

I think that's unfortunately true. And if you use a mix of passkeys and YubiKeys the UX is less than ideal.

[aarongoldenthal]

I tried the "Sign in with a passkey" option and Bitwarden does give the passkey popup, but does not find the passkey:

I tried deleting the passkey and recreating. Interestingly, when I just tried to create a new passkey, Bitwarden did note that there was a passkey already registered (and only allows one). I deleted the original both on the site and Bitwarden, everything seemed to save fine as it did before, but saw the same behavior. I also double checked and see the same behavior on Chrome and Firefox (both on Windows 11).

[miharekar]

Yeah, I’m aware it didn’t fix it, that’s why I didn’t even comment here.

I tried several different things but nothing made it work with Bitwarden. It works with 1Password, LastPass, Chromium native, Safari native, macOS Keychain, so at this point I’m blaming Bitwarden’s implementation 😅

I’m sorry to say that diving deep into Bitwarden browser code and writing Bitwarden specific hacks is very low on my priority list of things to do.

If anyone wants to tackle it, you’re more than welcome to, but I probably won’t do anything here anytime soon.