> ## Documentation Index
> Fetch the complete documentation index at: https://docs-dev-docs-event-stream-action-templates.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# MfaSmsChallenge
> Describes all the hooks and methods available to customize the Universal Login `mfa-sms-challenge` screen.
The `mfa-sms-challenge` screen prompts the user to enter a one-time code sent to their phone via SMS to complete MFA verification.
## 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.
```jsx Import Example theme={null}
// root import
import { useMfaSmsChallenge } from '@auth0/auth0-acul-react';
// partial import
import {
useMfaSmsChallenge,
// Context hooks
useUser,
useTenant,
useBranding,
useClient,
useOrganization,
usePrompt,
useScreen,
useTransaction,
useUntrustedData,
// Common hooks
useCurrentScreen,
useAuth0Themes,
useErrors,
// Utility hooks
useChangeLanguage,
useResend,
// Methods
continueMfaSmsChallenge,
getACall,
pickSms,
resendCode,
tryAnotherMethod,
} from "@auth0/auth0-acul-react/mfa-sms-challenge";
function MfaSmsChallengeScreen() {
const { continueMfaSmsChallenge } = useMfaSmsChallenge();
return (
);
}
```
## Context Hooks
Screen-scoped hooks that provide read-only access to Auth0 context data on the `mfa-sms-challenge` screen. Import them from `@auth0/auth0-acul-react/mfa-sms-challenge`.
() => BrandingMembers}>
This hook provides branding configurations, such as logo, colors, and theme settings displayed on the `mfa-sms-challenge` screen.
```jsx Example theme={null}
import { useBranding } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function CustomTheme() {
const branding = useBranding();
}
```
() => ClientMembers}>
This hook provides client-related configurations, such as `id`, `name`, and `logoUrl`, for the `mfa-sms-challenge` screen.
```jsx Example theme={null}
import { useClient } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function AppInfo() {
const client = useClient();
}
```
() => OrganizationMembers}>
This hook provides information about the user's Organization if the MFA flow is Organization scoped. Returns `null` when no Organization context is present.
```jsx Example theme={null}
import { useOrganization } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function OrgSelector() {
const organization = useOrganization();
if (!organization) {
return
No organization context
;
}
}
```
() => PromptMembers}>
This hook contains data about the current prompt in the authentication flow.
```jsx Example theme={null}
import { usePrompt } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function FlowInfo() {
const prompt = usePrompt();
}
```
() => ScreenMembersOnMfaSmsChallenge}>
This hook contains details specific to the `mfa-sms-challenge` screen, including its configuration and context.
```jsx Example theme={null}
import { useScreen } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function ScreenDebug() {
const screen = useScreen();
}
```
() => TenantMembers}>
This hook contains data related to the tenant, such as `id` and associated metadata.
```jsx Example theme={null}
import { useTenant } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function TenantInfo() {
const tenant = useTenant();
}
```
() => TransactionMembers}>
This hook provides transaction-specific data for the `mfa-sms-challenge` screen, such as the current MFA flow state.
```jsx Example theme={null}
import { useTransaction } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function TransactionInfo() {
const transaction = useTransaction();
}
```
() => UntrustedDataMembersOnMfaSmsChallenge}>
This hook handles untrusted data passed to the screen, such as prefilled values from URL parameters.
```jsx Example theme={null}
import { useUntrustedData } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function PrefilledForm() {
const untrustedData = useUntrustedData();
}
```
() => UserMembers}>
This hook provides details of the active user, including `username`, `email`, and available authentication methods.
```jsx Example theme={null}
import { useUser } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function UserProfile() {
const user = useUser();
}
```
MfaSmsChallengeMembers}>
This hook returns all methods and context available on the `mfa-sms-challenge` screen.
## Methods
This method submits the SMS one-time code to complete the MFA challenge.
```jsx Example theme={null}
import { useMfaSmsChallenge } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function VerifyCodeForm() {
const { continueMfaSmsChallenge } = useMfaSmsChallenge();
return (
);
}
```
**Method Parameters**
[MfaSmsChallengeOptions](/docs/libraries/acul/react-sdk/API-Reference/Types/interfaces/MfaSmsChallengeOptions).
The one-time code sent to the user's phone via SMS.
Whether to remember the device and skip MFA on future logins.
This method switches the MFA challenge to a voice call instead of SMS.
```jsx Example theme={null}
import { useMfaSmsChallenge } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function GetACallButton() {
const { getACall } = useMfaSmsChallenge();
return (
);
}
```
This method navigates to the SMS phone number selection screen.
```jsx Example theme={null}
import { useMfaSmsChallenge } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function PickSmsButton() {
const { pickSms } = useMfaSmsChallenge();
return (
);
}
```
This method resends the SMS one-time code to the user's phone.
```jsx Example theme={null}
import { useMfaSmsChallenge } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function ResendCodeButton() {
const { resendCode } = useMfaSmsChallenge();
return (
);
}
```
This method navigates to the MFA method selection screen so the user can choose a different authentication factor.
```jsx Example theme={null}
import { useMfaSmsChallenge } from '@auth0/auth0-acul-react/mfa-sms-challenge';
function TryAnotherMethodButton() {
const { tryAnotherMethod } = useMfaSmsChallenge();
return (
);
}
```
## Common/Utility Hooks
useResend} type="Hooks">
This hook manages resend cooldown state and logic for screens with resend code functionality.
useAuth0Themes} type="Hooks">
This hook gets the current theme options with flattened configuration from branding context.
useChangeLanguage} type="Hooks">
This hook returns a function for changing the display language on the current ACUL screen.
useCurrentScreen} type="Hooks">
This hook gets the current screen context and state.
useErrors} type="Hooks">
This hook reads and manages server, client, and developer errors on the screen.
## 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.
```jsx Import Example theme={null}
// root import
import { useMfaSmsChallenge } from '@auth0/auth0-acul-react';
// partial import
import {
useMfaSmsChallenge,
// Context hooks
useUser,
useTenant,
useBranding,
useClient,
useOrganization,
usePrompt,
useScreen,
useTransaction,
useUntrustedData,
// Common hooks
useCurrentScreen,
useAuth0Themes,
useErrors,
// Utility hooks
useChangeLanguage,
useResend,
// Methods
continueMfaSmsChallenge,
getACall,
pickSms,
resendCode,
tryAnotherMethod,
} from "@auth0/auth0-acul-react/mfa-sms-challenge";
function MfaSmsChallengeScreen() {
const { continueMfaSmsChallenge } = useMfaSmsChallenge();
return (
);
}
```
## Context Hooks
Screen-scoped hooks that provide read-only access to Auth0 context data on the `mfa-sms-challenge` screen. Import them from `@auth0/auth0-acul-react/mfa-sms-challenge`.