Creates an instance of the CustomizedConsent screen manager.
The constructor initializes the BaseContext and sets up the screen property
with an instance of ScreenOverride tailored for the customized consent screen.
Holds the specific screen data and properties for the Customized Consent screen,
processed by ScreenOverride. This includes scopes and authorizationDetails.
Static ReadonlyscreenThe unique identifier for the Customized Consent screen.
This static property is used by the SDK's BaseContext to ensure that the
class is instantiated in the correct screen context.
Utility 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'
});
Submits the user's decision to accept (grant) the requested permissions and authorization details.
This method prepares and posts form data to the /u/customized-consent?state=<transaction_state> endpoint
with action: "accept". The transaction state is automatically included in both the
URL query parameter and the form body.
Optionalpayload: Screens.CustomOptionsOptional. An object for any custom key-value pairs to be sent with the request. These parameters will be included in the form data submitted to the server.
A promise that resolves once the form submission is initiated. Typically, a successful submission leads to a server-side redirect.
Submits the user's decision to deny (reject) the requested permissions and authorization details.
This method prepares and posts form data to the /u/customized-consent?state=<transaction_state> endpoint
with action: "deny". The transaction state is automatically included in both the
URL query parameter and the form body.
Optionalpayload: Screens.CustomOptionsOptional. An object for any custom key-value pairs to be sent with the request. These parameters will be included in the form data submitted to the server.
A promise that resolves once the form submission is initiated. A successful submission usually results in a server-side redirect.
CustomizedConsent
Example