Discord passkey missing (it exists in vault but not found by Bitwarden)

[BakedCrossiant]

Steps To Reproduce

1. Go to 'discord.com/login'
2. Click on 'Log In'
3. Scroll down to 'or sign in with Passkey'
4. Click on 'or sign in with Passkey'

Expected Result

Successfully log-in and return to session.

Actual Result

Passkey not found.

Screenshots or Videos

Additional Context

No response

Operating System

Windows

Operating System Version

24H2

Web Browser

Firefox

Browser Version

137.0.2

Environment Versions

Version: 2025.3.2

SDK: 'main (50f5a17)'

Server version: 2025.4.1

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[S-Kakar]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-20449

[abergs]

Interesting, thanks for bringing this to us. Does the same thing happen in another browser? Did it use to work for you in FF?

[pamperer562580892423]

That may be a duplicate of #14139

[BakedCrossiant]

Interesting, thanks for bringing this to us. Does the same thing happen in another browser? Did it use to work for you in FF?

• No, it hasn't ever worked in Firefox, it's similar to the behaviour I've experienced using the Android application, to be honest. This screenshot is from MS Edge

[abergs]

I noticed your vault item has the domain dicordapp.com but you're trying to sign in at dicord.com. I think that is why it doesn't work, as passkeys are bound to the exact domain name (adding URLs to the vault item does not change this).

[BakedCrossiant]

The thing is, once I bypass the login screen (after signing in using a different method), the passkey is recognised in the Discord web app.

All of these screenshots have the same discord.com URI

[abergs]

Could you try re-creating the passkey? As in - removing it from discord and then creating a new one?

[BakedCrossiant]

• Discord gives this error when trying to re-establish a new passkey

[Kusko25]

Chiming in with the same issue, but interesting thing is the passkey can be used for 2fa when logging in with username and password

[escape0707]

Related issue.

[holow29]

This issue is likely the same as #14139 which affects AWS, Wells Fargo, Discord, and others. In these cases, there is a button to sign in with a passkey, the BW UI opens, but no passkeys are found.

Related issue.

That issue is now actually different because LinkedIn now uses a conditional UI to sign in with passkeys (not as shown in the OP of that issue - at the time of OP it was likely the same as this issue). That issue is now more closely aligned with the eBay one (#7785). In these cases, there is no button to sign in with a passkey, there is instead a browser pop-up in the username field of the login form that says, "Use a passkey." Clicking that does not open the BW UI.

@abergs This is only my understanding of these two main sets of unresolved issues with end-user passkey use. Unfortunately, they make passkeys unusable across many major websites, and I'm sure the people who want to make passwordless authentication happen would love to see them prioritized and subsequently resolved to make Bitwarden usable.