Skip to main content
The login-id screen collects the user’s identifier as the first step of an identifier-first authentication flow. Depending on your tenant, this identifier can be an email, phone number, or username. It also supports passkey login, federated identity providers, and Google One Tap.

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 the login-id screen. Import them from @auth0/auth0-acul-react/login-id.
useBranding
This hook provides branding configurations, such as logo, colors, and theme settings displayed on the login-id screen.
Example
useClient
This hook provides client-related configurations, such as id, name, and logoUrl, for the login-id screen.
Example
useOrganization
This hook provides information about the user’s Organization if the login is Organization scoped. Returns null when no Organization context is present.
Example
usePrompt
This hook contains data about the current prompt in the authentication flow.
Example
This hook contains details specific to the login-id screen, including its configuration and context.
Example
useTenant
This hook contains data related to the tenant, such as id and associated metadata.
Example
useTransaction
This hook provides transaction-specific data for the login-id screen, such as active connections, available login methods, and current flow state.
Example
useUntrustedData
This hook handles untrusted data passed to the screen, such as a prefilled identifier from URL parameters.
Example
useUser
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 login-id screen.

Methods

googleOneTap
Promise<void>
This method authenticates the user using a Google One Tap credential, enabling one-click sign-in without redirecting to a separate login page.
Example
Method Parameters
federatedLogin
Promise<void>
This method redirects the user to the Social or Enterprise Identity Provider (IdP) for authentication.
Example
Method Parameters
login
Promise<void>
This method submits the user’s identifier to proceed to the next step in the authentication flow.
Example
Method Parameters
passkeyLogin
Promise<void>
This method initiates passwordless authentication using a passkey.
Example
Method Parameters
pickCountryCode
Promise<void>
This method navigates to the country code picker for phone-based login flows.
Example

Common/Utility Hooks

This hook gets the current theme options with flattened configuration from branding context.
This hook returns a function for changing the display language on the current ACUL screen.
This hook gets the current screen context and state.
This hook reads and manages server, client, and developer errors on the screen.
This hook returns a list of active identifier types (email, phone, username) in the current flow.
This hook enables passkey autofill on an input field for a seamless passwordless login experience.