id
, nickname
, email
, and password
. To learn about Auth0’s user profile schema, read Normalized User Profiles. To learn more about updating user profiles, read Update User Profiles Using Your Database.Parameter | Definition |
---|---|
Name | The name of the connection. The name must start and end with an alphanumeric character, contain only alphanumeric characters and dashes, and not exceed 35 characters. |
Requires Username | Forces users to provide a username and email address during registration. |
Username Length | Sets the minimum and maximum length for a username. |
Disable Sign Ups | Prevents signups to your application. You will still be able to create users with your API credentials or via the Auth0 Dashboard. |
login
script; additional scripts for user functionality are optional.
The available database action scripts are:
Name | Description | Parameters |
---|---|---|
Login Required | Executes each time a user attempts to log in. | email , password |
Create | Executes when a user signs up. | user |
Verify | Executes after a user follows the verification link. | email |
Change Password | Executes when a user clicks on the confirmation link after a reset password request. | email , newPassword |
Get User | Retrieves a user profile from your database without authenticating the user. | email |
Delete | Executes when a user is deleted using the API or Auth0 Dashboard. | id |
id
(or alternatively user_id
) property in the returned user profile will be used by Auth0 to identify the user.If you are using multiple custom database connections, then id
value must be unique across all the custom database connections to avoid user ID collisions. Our recommendation is to prefix the value of id
with the connection name (omitting any whitespace). To learn more about user IDs, read Identify Users.email == user.email
.
With the bcrypt.compareSync
method, it then validates that the passwords match, and if successful, returns an object containing the user profile information including id
, nickname
, and email
.
This script assumes that you have a users
table containing these columns. The id
returned by Login script is used to construct the user ID attribute of the user profile.
context
parameter in the script signature to make Organization details like id
, name
, and metadata
available to your custom database action scripts. Organization data is passed in the context object when the associated action happens in the context of an organization; for example, when a user authenticates on an organization’s login prompt, the login action script is passed. To learn more, read Database Connections.
context
object to your custom database action scripts, inserted directly preceding the callback parameter. When events are triggered with Organization context, the corresponding data is made available to your custom database action scripts in the format below:
delete
script.configuration
object in your database action scripts (i.e., configuration.MYSQL_PASSWORD
).
Use the added parameters in your scripts to configure the connection. For example, you might add the following to the MySQL Login script: