signup 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 Signup 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 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
signup 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
signup 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
getErrors
This method retrieves the array of transaction errors from the context, or an empty array if none exist. An array of error objects from the transaction context.
getSignupIdentifiers
This method returns the list of enabled identifiers for the signup form,
marking each as required or optional based on transaction config. An Array of identifier objects (e.g., email, phone, username).
Example
Example
Example
validatePassword
This method returns an object of type PasswordValidationResult indicating whether the password is valid and why.Method Parameters
validateUsername
This method validates a given username against the current username policy defined in the transaction context. It returns an object indicating whether the username is valid and why.Method Parameters
Example