Use cases
Use Custom Enrollment Tickets for:- Onboarding new users
- Configuring user settings
- Specifying factors you want customers to choose during enrollment
- Allowing users to enroll more than one factor
Configure Custom Enrollment Tickets
Make a post call to ’s/guardian/post_ticket
endpoint.
Parameter | Required | Description |
---|---|---|
allow_multiple_enrollments | Optional | Allows a previously enrolled user to enroll with additional factors, excluding email. |
factor | Optional | Specifies which factor the user must enroll with, excluding email. Used with allow_multiple_enrollments , can specify more than one factor for enrollment. |
These parameters can only be used with Universal Login and cannot be used with Classic Login or custom MFA pages.
ticket_id
and a ticket_url
. The ticket_id
is for internal use. Deliver the ticket_url
to the user with the send_email
parameter to kick off the enrollment process. Tickets expire after 5 days and are single-use. A user who receives a ticket will only be able to enroll once.
Sample response:
auth0-custom-domain
HTTP header. To learn more, review Multiple Custom Domains.
Custom Enrollment Tickets with Classic Login
If you are using the Classic Login experience and need to customize how the page looks when the user navigates to theticket_url
, you can edit the MFA page.
- Navigate to Dashboard > Branding > Universal Login > Advanced options > Multi-factor Authentication.
- If Customize MFA Page is not selected, toggle this option on.
- Update the
ticket
variable. Example: