Skip to main content
Enabling Flexible Identifiers on your tenant has the potential to introduce breaking changes to your production environment. For more information on potential problems and limitations, read Flexible Identifiers and Attributes.
An Attribute for database connections, email, phone number, or username, is part of the Flexible Identifiers. End users sign up, authenticate, and reset passwords with an Attribute. Each Attribute has a unique configuration.

​
Activate Attributes

  1. Navigate to Auth0 Dashboard > Authentication > Database.
  2. Select +Create DB Connection.
  3. Enter a name for the connection and choose the attributes.
  4. Choose the authentication method for the connection.
Default values are assigned to a new connection and can be edited after the connection has been created.
SettingValue
Use {attribute} as IdentifierTrue
Allow Signup with {attribute}Required
Require {attribute} on user profileTrue
Username LengthMin: 1 Max: 15
Allow usernames in email formatFalse
Allow usernames in phone number formatFalse

​
Configure Attributes

Select the Attributes tab on the connection. Choose from the available Attributes and select Configure. Once you’ve updated Attribute configurations, select Save.
Option
Use Email as IdentifierTurning this on will make email an identifier for this connection. Users will be able to use email for login and password reset.
Verification MethodChoose Email Verification link or One-Time Password (OTP).
Allow Signup with EmailChoose how email will be collected at signup
  • Off: Attribute will be blocked from signup flows.
  • Optional: Attribute will be optional on signup flows.
  • Required: Signup flows will fail if the attribute is not present.

Signup flows include:
  • Universal Login
  • Authentication API dbconnections/signup endpoint
Verify email on sign upUsers will be asked to verify their email address via magic link when signing up.
Require email on user profileRequires email to be present across all operations that create or update a user profile on this connection.
Will require email is present on the following:
  • Signup flows
  • Creating or updating a user via the Management API
  • Bulk user import
Option
Use Username as IdentifierTurning this on will make username an identifier for this connection. Users will be able to use username for login and password reset.
Allow Signup with UsernameChoose how the username will be collected at signup
  • Off: Attribute will be blocked from signup flows.
  • Optional: Attribute will be optional on signup flows.
  • Required: Signup flows will fail if Attribute is not present.

Signup flows include:
  • Universal Login
  • Authentication API dbconnections/signup endpoint
Require username on user profileRequires username to be present across all operations that create or update a user profile on this connection.
Will require username is present on the following:
  • Signup flows
  • Creating or updating a user via the Management API
  • Bulk user import
Username LengthSet the minimum and maximum values allowed for a user to have as username.
Option
Use Phone Number as IdentifierTurning this on will make phone_number an identifier for this connection. Users will be able to use phone_number for login and password reset.
Allow Signup with Phone NumberChoose how the phone number will be collected at signup
  • Off: Attribute will be blocked from signup flows.
  • Optional: Attribute will be optional on signup flows.
  • Required: Signup flows will fail if attribute is not present.

Signup flows include:
  • Universal Login
  • Authentication API dbconnections/signup endpoint
Verify phone on signupUsers will be required to verify their phone number via OTP when signing up.
Please ensure you have configured a phone provider or your users will not be able to proceed with signing up.
Require phone on user profileRequires phone to be present across all operations that create or update a user profile on this connection.
Will require phone is present on the following:
  • Signup flows
  • Creating or updating a user via the Management API
  • Bulk user import

​
Configure or remove existing Attributes on a connection

All Attributes can be changed or deleted from your . Users cannot log in, sign up or reset passwords using the removed Attribute, and a minimum of one Attribute must remain active on every connection. To change or remove an Attribute, navigate to the Attributes tab, then choose Remove.

​
Revert a connection

To revert a connection back to its original state, use the Update a connection endpoint with an options object that does not include the attributes parameter, as shown below.
  • If you use the options parameter, the entire options object is overridden. To avoid partial data or other issues, ensure all current parameters are present by copying the contents within the connections options object and including it in the PATCH call. The only parameter you should remove is attributes.
  • If your tenant has username enabled as an Attribute, performing the following action requires you to modify your username settings. You’ll need to reconfigure your username settings if you choose this path.
{
"options": {
       }
}