Configure Auth0 Passkeys for Users with Non-Unique Emails in a Connection
Last Updated:
Overview
Users in Auth0 connections containing non-unique emails experience login failures after successfully setting up Passkeys. This occurs because Passkeys default to using email addresses as identifiers, which causes conflicts when emails are not unique. To resolve this, configure the connection to use unique usernames as flexible identifiers and enable either the custom database Import Mode or the early access Context Object feature.
Applies To
* Auth0
* Passkeys
* Username login
* Non-unique emails
* Custom database connections
Cause
Passkeys default to using email addresses as identifiers. When a custom database connection contains non-unique emails, this default configuration causes conflicts and subsequent login failures.
Solution
How are Auth0 Passkeys configured for users with non-unique emails?
Configure the connection to use usernames as flexible identifiers and enable the necessary database settings to resolve the login failures.
- Enable flexible identifiers at the connection level, remove email as an option, and enable Username as the flexible identifier for the connection.
- Select Identifier First under the Authentication Profile.
- Enable either the early access feature Use your own database without user import enabled or turn on the custom database Import Mode.
