Hosted Login v2 screens text reference
Use JTL (Janrain Templating Language) tags to modify your Hosted Login v2 screens. JTL tags determine the wording of the text elements that appear on those screens.
Screen | Screen ID | Description |
---|---|---|
authRule_secondFactor | Appears after:
| |
registrationSuccess | Appears after a user has successfully created a new account. | |
deleteAccountSuccess | Appears when a user clicks the Delete My Account button found in his or her user profile. | |
authRule_reqAttrs | Appears if:
| |
socialRegistration | Appears at the end of the social registration workflow. | |
traditionalRegistration | Appears if a user elects to create a new account by using traditional registration. | |
verifyEmailSuccess | Appears after a user has successfully verified his or her email address by using a Customer Care Portal email verification link. | |
verifyEmail | Appears when a user clicks an invalid email verification link. | |
resendVerificationSuccess | Appears after a user enters an email address on the verifyEmail screen and then clicks Send. | |
resetPasswordSuccess | Appears when a user clicks the Forgot Password? link on the signIn screen. | |
authRule_secondFactorLoginCode | Appears if:
| |
logoutSuccess | Appears after a user successfully logs out. | |
manageProfile_security | Appears after a user clicks Account Security on the manageProfile screen. | |
manageProfile_privacy | Appears after a user clicks Privacy Settings on the manageProfile screen. | |
manageProfile | Appears after a user clicks a link for managing his or her user profile. | |
Appears after a user clicks Personal Data on the manageProfile screen. | ||
mergeAccounts | Appears if a user created their initial account by using traditional registration, then later tries to sign in with a social login provider that uses the same email address as the one found in the initial account. | |
traditionalAuthenticateMerge | The traditionalAuthenticateMerge screen is the last step in the merge accounts workflow. This screen appears if:
The traditionalAuthenticateMerge screen then appears and the user is asked to enter his or her Identity Cloud email address and password. After doing so, the user will Ā be able to sign-in using either their Identity Cloud account or their Twitter account. | |
resetPasswordSuccess | Appears after a user successfully changes their password on the Reset Password screen. | |
resetPasswordRequestSuccess | Appears after a user has submitted his or her email address on the resetPassword screen. | |
resetPasswordCodeExchange | Appears if a user attempts to reset his or her password using an invalid reset password code. This typically occurs when the code has expired or when the code has already been used. | |
authRule_secondFactorRegistrationCode | Appears:
If two-factor authentication is in force then, after the account has been created, a 2FA access code is sent to the email address associated with the account. The user must enter that access code and then click Continue to complete the registration and login process. | |
requestDataSuccess | Appears if a user clicks the Request My Data button on the Privacy Settings screen. | |
resetPassword | Appears after a user has clicked a link in a reset password email. | |
signIn | By default, the first screen that appears when a user clicks a link for logging on to or registering with a site. | |
loginSuccess | Appears after a user successfully logs in. | |
authRule_acceptLegal | Appears if:
The user must agree to the legal acceptances before they are allowed to log in. | |
visitingMessage | Appears after a user has successfully verified their email address or successfully reset their password: a āsuccessā screen appears for a few seconds and is then replaced by the vistingMessage screen. | |
authRule_consents | Appears if:
|
Updated 2 months ago