Microsoft Edge browser extension's passkey implementation unreliable?

I have started to use passkeys with a few websites that support them but have found Bitwarden to be unreliable in accepting and storing new passkeys and providing passkeys to websites.

My experiences are with the Microsoft Edge browser, on both Windows 11 and MacOS platforms. In all cases both Edge and Bitwarden’s Edge extension are up-to-date. The issue is the extension sometimes works and sometimes doesn’t when either you want to receive and store a new passkey or provide a passkey to a website that is requesting one. About 40% of the time it works, with the Bitwarden UI appearing, but 60% of the time the Edge browser’s built-in handling of passkeys appears to be triggered instead of the Bitwarden extension. Since I use and want to continue to use Bitwarden to store the passkeys, this is problem.

I have confirmed many times that ‘Make Bitwarden your default password manager’ is checked and enabled in the extension’s settings (under auto-fill). I have ensured all of Edge’s own password management functionality is disabled. I have restarted the browser, etc. I experience the same success/failure rates on both Windows 11 and MacOS (14.6.1) platforms.

Is this a bug in the extension, a bug in the browser, or am I doing something wrong or haven’t configured something correctly?

All the other Bitwarden browser extension functionality like auto-fill works 100% correctly all the time. It is only the passkey functionality I am experiencing issues with.

1 Like

@Airtime Did you check in the extension the following:

  1. Settings → Notifications → “Ask for passkey…” is checked?
  2. Settings → Notifications → Excluded domains → if there are domains on that list you want to use with passkeys, delete those domains here in this “excluded domains” list

?

Yes, ‘Ask to save and use passkeys’ is checked and enabled. There are no excluded domains.

Oh… I’m not sure if there can be other reasons for this (PS: I don’t use Edge myself - and don’t see what you describe on Brave and Windows 11), but I would tend to advise you to report it on GitHub as a possible bug then. (GitHub - bitwarden/clients: Bitwarden client apps (web, browser extension, desktop, and cli).)

I saw this problem in edge. For me it was solved in the “wallet” settings, under “passwords” > “View and autofill passwords and passkey” - disable this option.

edge://wallet/settings

Hope this helps

2 Likes

Thank you! This worked for me, but I had to disable all of Edge’s password-related options, including the “”“Show the “Reveal password” button in password fields”“” which did not look relevant to me. (Or it could be something else, the only thing that I’m sure of is that disabling “View and autofill passwords and passkey” did not work at first.)

1 Like