reset-password-mfa-email-challenge screen is displayed during the password reset flow when multi-factor authentication is required via email. It prompts the user to enter a verification code sent to their email address to continue the reset process.

Import
Each screen has its own set of hooks and methods. The SDK supports partial import and root import for each screen.- Using partial import allows you to include only the code you need for your specific use case.
- Using root import allows you to load all screens from a single bundle, which is useful when you want a unified build to handle all possible screens.
Import Example
Context Hooks
Screen-scoped hooks that provide read-only access to Auth0 context data on thereset-password-mfa-email-challenge screen. Import them from @auth0/auth0-acul-react/reset-password-mfa-email-challenge.
() => BrandingMembers
This hook provides branding configurations, such as logo, colors, and theme settings displayed on the
reset-password-mfa-email-challenge screen.Example
() => ClientMembers
This hook provides client-related configurations, such as
id, name, and logoUrl, for the reset-password-mfa-email-challenge screen.Example
() => ExperimentMembers
This hook provides the active Experiment Center experiment for the
reset-password-mfa-email-challenge screen, or null when no experiment is active (or the screen has not opted in via context_configuration).Example
() => OrganizationMembers
This hook provides information about the user’s Organization if the password reset is Organization-scoped. Returns
null when no Organization context is present.Example
() => PromptMembers
This hook contains data about the current prompt in the authentication flow.
Example
This hook contains details specific to the
reset-password-mfa-email-challenge screen, including its configuration and context.Example
() => TenantMembers
This hook contains data related to the tenant, such as
id and associated metadata.Example
() => TransactionMembers
This hook provides transaction-specific data for the
reset-password-mfa-email-challenge screen, such as active connections and current flow state.Example
() => UntrustedDataMembers
This hook handles untrusted data passed to the screen, such as a prefilled email or username from URL parameters.
Example
() => UserMembers
This hook provides details of the active user, including
username, email, and available authentication methods.Example
This hook returns all methods and context available on the
reset-password-mfa-email-challenge screen.Methods
This method submits the email verification code to continue the MFA step in the password reset flow.Method Parameters
Example
Resends the verification code to the user’s email address.This method submits a form to Auth0. Auth0 renders this screen again, so the browser reloads the page and React state, effects, and timers are 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
useErrors()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.
useResend(). The useResend() hook stores the countdown in localStorage, so the countdown persists across the page reload.Example
Common/Utility Hooks
Manages the resend cooldown for this screen. The hook returns the remaining seconds, whether resending is disabled, and a
startResend() function that triggers the resend and starts the cooldown. The countdown persists across the page reload that a resend causes.