Passkeys no longer working with Auth0

Get Help
,
1

Hello,

I’ve reported an issue on Bitwarden, because Passkeys are no longer accepted by Auth0.

They told me to raise the same issue here as well.
Can we have some feedback from Auth0 regarding this problem, because I can only log in with recovery codes at the moment.

3

Hi @Arne_De_Herdt

This is a known compatibility issue affecting passkey authentication in specific browser and platform combinations, and Auth0 Support should investigate your specific tenant configuration and browser environment.

Root Cause: Auth0’s passkey support uses WebAuthn, which has varying levels of support across browsers and platforms. Firefox on macOS has historically had inconsistent passkey support, particularly with third-party password managers like Bitwarden. Additionally, Firefox’s Total Cookie Protection feature can interfere with authentication flows, and some password manager integrations (like 1Password) have reported compatibility issues with Auth0’s device biometrics authentication.

This behavior is largely governed by how your browser and operating system handle WebAuthn requests, as Auth0 relies on the standard browser prompt for authenticator selection rather than controlling the UI directly. Here are a few workarounds that often resolve this conflict:

  1. Confirm the Passkey Saved: First, open your Bitwarden vault and confirm the passkey is actually listed under the correct entry for this site. Occasionally, the save step can appear successful but fail to complete fully.

  2. Check Bitwarden Extension Settings: In your Bitwarden browser extension, go to Settings > Options, and ensure Ask to save and use passkeys is enabled.

  3. Bypass the OS Prompt: When the Windows Security dialog appears, look for a link such as More choices, Use a passkey from a different device, or simply Cancel to dismiss the native prompt. In some cases, dismissing this allows Bitwarden to surface its own passkey picker.

  4. Check Chrome’s Passkey Settings (if using Chrome): Navigate to chrome://password-manager/settings and ensure Google Password Manager is not set as the default passkey provider, as this can suppress third-party managers like Bitwarden.

If necessary, I will ask you for more information in order to open a support ticket on your behalf so that our engineering team can investigate this further.

Kind Regards,
Nik