StaticscreenUtility FeatureChanges the language/locale for the current authentication flow.
This method triggers a language change by submitting the new locale preference to the server with the 'change-language' action. The language change will cause the current screen to re-render with the new locale.
Language change options including the target language code
Options for changing the language/locale during the authentication flow
Additional custom fields to be submitted along with the language change. Custom fields should be prefixed with 'ulp-'.
Short language name (locale code) to be set (e.g., 'en', 'fr', 'es').
Optionalpersist?: "session"Defines persistence scope for the language preference. Currently only 'session' is supported.
A promise that resolves when the form submission is complete
import LoginId from "@auth0/auth0-acul-js/login-id";
const loginManager = new LoginId();
// Change language to French
await loginManager.changeLanguage({
language: 'fr',
persist: 'session'
});
import LoginPassword from "@auth0/auth0-acul-js/login-password";
const loginPasswordManager = new LoginPassword();
// Change language to Spanish with additional custom data
await loginPasswordManager.changeLanguage({
language: 'es',
persist: 'session',
'ulp-custom-field': 'custom-value'
});
Requests a new verification code for the user's email address.
Optionalpayload: Screens.CustomOptionsOptional custom parameters to send with the request.
A promise that resolves once the form is submitted, before the new page loads. It doesn't confirm that a new code was sent.
Submits a form POST with action: "resend-code". Auth0 responds by rendering this
screen again, or the interstitial-captcha screen if a captcha is required. Either
way the browser loads a new page, and the current JavaScript context, including
component state and timers, is lost.
Code after await resendCode() may still run, but anything it sets up, such as a
"code sent" message or a countdown, is gone after the reload. If the resend fails,
for example because of a rate limit, Auth0 renders this screen again without an
error, so that it doesn't reveal whether the user exists. Nothing appears in
transaction.errors, and the returned promise doesn't reject.
To add a cooldown between resends, use resendManager(). It stores its countdown
in localStorage, so the countdown survives the reload.
It also disables resending when screen.data.resendLimitReached is true.
Utility FeatureGets resend functionality with timeout management for this screen
Optionaloptions: Screens.StartResendOptionsConfiguration options for resend functionality
Options for configuring resend functionality
OptionalonStatusChange?: Screens.OnStatusChangeCallbackOptionalonTimeout?: () => voidOptionaltimeoutSeconds?: numberResendControl object with startResend method
import EmailIdentifierChallenge from '@auth0/auth0-acul-js/email-identifier-challenge';
const handleStatusChange = (remainingSeconds, isDisabled) => {
setDisabled(isDisabled);
setRemaining(remainingSeconds);
};
const handleTimeout = () => {
console.log('Timeout completed, resend is now available');
};
const { startResend } = emailChallenge.resendManager({
timeoutSeconds: 15,
onStatusChange: handleStatusChange,
onTimeout: handleTimeout
});
// Call startResend when user clicks resend button
await startResend();
Optionalpayload: Screens.CustomOptionsOptionalpayload: Screens.CustomOptions
Optional on the interface so existing implementors of
BaseMembers(e.g. test mocks) keep compiling. Always populated at runtime by theBaseContextconstructor.