Creates an instance of the PendingConsent screen.
Optional on the interface so existing implementors of BaseMembers (e.g. test mocks)
keep compiling. Always populated at runtime by the BaseContext constructor.
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'
});
Continues the flow once the pending consent has been resolved off-browser.
Optionalpayload: Screens.CustomOptionsOptional custom options to include with the request.
Submits a form POST with the transaction state and no action. Auth0 reads the
approve/deny outcome from the consent status, not from the request body, so there is
no separate accept or deny action. If the consent is still pending, Auth0 renders this
screen again instead of redirecting, and the page reloads.
Utility FeatureStarts and manages polling for the pending-consent status.
Creates a polling session that repeatedly checks the pending-consent endpoint
at the specified interval until the consent is resolved off-browser or an error occurs.
The consent counts as resolved when it has been either approved or denied. At that point
the provided onCompleted callback is invoked and
polling stops automatically. Call continue() from onCompleted to advance the flow.
Auth0 then applies the approve/deny outcome.
Use the returned MfaPushPollingControl to start, stop, or check the status of the polling process at any time.
Configuration options for the polling process:
intervalMs — Optional polling interval in milliseconds (defaults to SDK’s internal value, typically 5000 ms).onCompleted — Optional callback fired when the consent has been approved or denied.onError — Optional callback fired when a polling error occurs, receiving an Error.A MfaPushPollingControl instance exposing:
startPolling() — Starts or resumes polling.stopPolling() — Cancels polling immediately.isRunning() — Indicates whether polling is currently active.import PendingConsent from '@auth0/auth0-acul-js/pending-consent';
const pendingConsent = new PendingConsent();
// Poll every 5 seconds until the consent is approved or denied off-browser
const control = pendingConsent.pollingManager({
intervalMs: 5000,
onCompleted: () => pendingConsent.continue(),
onError: (error) => console.error('Polling error:', error),
});
control.startPolling();
// Later, cancel polling if needed
control.stopPolling();
startPolling() multiple times; it has no effect if already running.continue().
Auth0 then checks the consent status again. Don't show it while polling is running, or
it can race the automatic continue() from onCompleted.
Class implementing the Pending Consent screen functionality. This screen is a waiting room shown during Rich Authorization Requests (RAR) flows when no customized-consent prompt is configured. The user approves or denies the request off-browser through the My Account experience while this screen polls for the outcome.