📘

If you're looking for the Hosted Login v1 version of this screen, see Terms of Service v1.

The authRule_acceptLegal screen appears if:

1. An authorization rule has been implemented that requires a user to agree to the required legal acceptances before he or she can log on.

2. The user has not yet agreed to these legal acceptances. Out of the box the Identity Cloud supports two legal acceptances: an organization’s privacy policy and its terms of use. By agreeing to the legal acceptances, the user agrees to both the privacy policy and the terms of use.

Legal acceptances are managed by using the legalAcceptances schema attribute. If the authorization.rules.legal_accepted authorization rule has been enabled:

1. A user signs in and is authenticated.

2. Before the user is issued an access token, the Identity Cloud checks the user profile to see if the legal acceptances have been agreed to:

   • If the user has agreed to the legal acceptances then he or she is issued an access token and is fully logged on.

   • If the user has not agreed to the legal acceptances, then the authRule_acceptLegal screen is displayed. The user must click Continue and agree to the legal acceptances before he or she is issued an access token.

Incidentally, authorization rules are processed in the following order:

1. authorization.rules.required_attributes
2. authorization.rules.min_age
3. authorization.rules.legal_acceptances
4. authorization.rules.consents
5. authorization.rules.email_is_verified

Authorization rules screen flow

The following graphic shows how the authRule_acceptLegal screen fits into the Authorization Rules flow:

See also

• The Terms of Service screen (authRule_acceptLegal) CSS
• The Terms of Service screen (authRule_acceptLegal) text reference