The LoginId class implements theDocumentation Index
Fetch the complete documentation index at: https://docs-dev.auth0-mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
login-id screen functionality. This screen collects the user’s identifier and password. Depending on your tenant, this identifer can be an email, phone number, or username.

Constructors
Create an instance of LoginId screen managerExample
Properties
branding
Provides branding-related configurations, such as branding theme and settings.
client
Provides client-related configurations, such as
id, name, and logoUrl, for the login-id screen.organization
Provides information about the user’s organization, such as organization
id and name.prompt
Contains data about the current prompt in the authentication flow.
screen
Contains details specific to the
login-id screen, including its configuration and context.tenant
Contains data related to the tenant, such as
id and associated metadata.transaction
Provides transaction-specific data for the
login-id screen, such as active identifiers and flow states.untrustedData
Handles untrusted data passed to the SDK, such as user input during login.
user
Details of the active user, including
username, email, and roles.Methods
Example
Example
redirect_url.
Example
Example
navigator.credentials.get() with mediation: "conditional". When supported,
this allows the browser to display stored passkeys directly within the username
field’s autocomplete dropdown.
Call this once when the login screen is initialized (for example, on page load).
After registration, focusing the username input will automatically display
matching passkeys as suggestions. Selecting a passkey completes authentication
without requiring additional user interaction.
Example
inputId is provided, the SDK will:
- Validate that the element exists and is an
<input>. - Overwrite its
autocompleteattribute with"webauthn username".
inputId, you are responsible for configuring
the input element manually with the correct attributes:
- The
autocompleteattribute must exactly contain"webauthn username". Including unrelated tokens such as"email"or"text"will prevent browsers from showing the passkey dropdown. - Overwriting the attribute is intentional and required for consistent behavior across browsers. Do not rely on merging or extending existing autocomplete values.
- If Conditional Mediation is not supported by the browser, the SDK will safely no-op.
registerPasskeyAutofill() utility,
returning a background AbortController to manage request lifetime. It should
only be invoked once per page lifecycle.
getErrors
This method retrieves the array of transaction errors from the context, or an empty array if none exist.
getLoginIdentifiers
This method gets the active identifier types for the login screen.
Example