Do passkeys work with the Firefox addon?

My Github credentials are in BitWarden and I can log into GitHub no problem.

But when I create a passkey in GitHub, BitWarden doesn’t do anything at all, the passkey creation process just sits there with a message saying ‘waiting for your browser addon to respond’.

Does this work at all?

It works for me just now. Used Windows 10 and latest FF & BW extension.

@Neutrino-Sunset Hi!

As @DoctorB already (implicitly :wink:) suggested, first step would be to make sure you have the latest versions of Firefox and the Firefox Bitwarden extension (or at least: your versions shouldn’t be older than some months… latest versions: Firefox 130.0, Bitwarden extension for Firefox: 2024.8.2).

Then, make sure in the Bitwarden extension the following option is turned on:
→ Settings → Notifications → Ask to save and use passkeys

And at last, make sure that the desired domains (in your case now: the GitHub domain) is not in this list (–> if it is, delete the domain in this list):
→ Settings → Notifications → Excluded domains

BitWarden is up-to-date (2024.8.2), and Ask to save and use passkeys is checked.
Firefox is up-to-date (130).
I have no sites with notifications blocked.
UBlock is disabled
Enhanced Tracking Protection disabled
Win 11

I click Add a passkey, enter the code I’m asked for then see this every time.

It works with Edge straight away. But if I try to login in Firefox using a passkey I created in Edge I see this

When that times out I see this (sorry for multiple posts, new user limits)

I am seeing a CSP error in the console, but I don’t know whether that’s significant.

Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src https://github.githubassets.com”```

I also enabled Windows Hello since I came across an article that suggested it needed to be enabled for the browser to report passkey support, but that didn't work.

Tried it on a Win10 system using same Firefox account, same BitWarden account, and same GitHub account, and it worked instantly.

Okay but then your initial question “Does this work at all?” seems to be answered, as it does seem to work for you in general, but not on your Windows 11, right?

I just tested it on my Windows 11, with latest Brave and latest Firefox (and latest versions of the corresponding Bitwarden extensions).
First test: my recently newly generated passkey (via Brave) for GitHub, stored in Bitwarden, worked fine when I logged in via Firefox.
Then I deleted the passkey in my Bitwarden vault and in GitHub and created it new via Firefox, without problem. Afterwards I can login to GitHub with this new passkey with both extensions - Brave and Firefox - again without any problem.

So, whatever this is on your machine - it is not a general problem (or impossibility), it seems.

Ok, so you’re correct, my initial question is answered.

The implicit question remains though, which is: does anyone have any idea why this might be happening, and what further steps can I take to diagnose the cause of the issue?

I got it working. I wondered whether the Firefox Multi-account container feature might be part of the problem, so I created a new Firefox window outside of any container and tried it there, and it worked!

In that new window I then opened a container tab and tried it there, and that worked too!

So it’s just one Firefox window I have open that it doesn’t work in, which is a bit odd since I have rebooted my laptop several times while trying to fix this, but no matter, I’ll just recycle that window.

1 Like