Skip to main content
The ResetPasswordMfaSmsChallenge class implements the reset-password-mfa-sms-challenge screen functionality. This screen prompts the user to enter the verification code sent to their phone via SMS as part of the MFA step during a password reset flow.

Constructors

Create an instance of ResetPasswordMfaSmsChallenge screen manager:
Example

Properties

Provides branding-related configurations, such as branding theme and settings.
Provides client-related configurations, such as id, name, and logoUrl, for the reset-password-mfa-sms-challenge screen.
Provides country code data for phone number entry, such as available and recommended, for the reset-password-mfa-sms-challenge screen.
The active Experiment Center experiment for this screen, or null when no experiment is active (or the screen has not opted in via context_configuration).
Provides information about the user’s Organization, such as id and name.
Contains data about the current prompt in the authentication flow.
Contains details specific to the reset-password-mfa-sms-challenge screen, including its configuration and context.
Contains data related to the tenant, such as id and associated metadata.
Provides transaction-specific data for the reset-password-mfa-sms-challenge screen, such as active identifiers and flow states.
Handles untrusted data passed to the SDK, such as user input during the MFA challenge flow.
Details of the active user, including username, email, and roles.

Methods

Promise<void>
This method changes the display language of the Universal Login page.
Example
Method Parameters
Promise<void>
This method submits the SMS verification code to continue the MFA challenge during the password reset flow.
Example
Method Parameters
Promise<void>
This method switches the user to voice call verification instead of SMS.
Example
This method retrieves the array of transaction errors from the context, or an empty array if none exist.
Promise<void>
Resends the SMS verification code to the user’s phone number.This method submits a form to Auth0. Auth0 renders this screen again, so the browser reloads the page and the JavaScript context, including component state and timers, is lost.When you call resendCode(), keep the following in mind:
  • Code that runs after await resendCode() can’t rely on state that the code sets, such as a “code sent” message or a countdown.
  • Server-side errors, such as rate limits, appear in transaction.errors after the page reloads. These errors don’t reject the returned promise.
  • The returned promise resolves when the form is submitted, before the page reloads. The promise doesn’t confirm that Auth0 sent a new code.
To add a cooldown between resends, use resendManager(). The resendManager() method stores the countdown in localStorage, so the countdown persists across the page reload.
Example
Returns a ResendControl object that manages resending with a cooldown. The startResend() method of the object triggers the resend and starts a cooldown period before the user can resend again. The countdown persists across the page reload that a resend causes.
Example
Method Parameters
Promise<void>
This method allows the user to select a different MFA method to complete the challenge.
Example