Configuration

Controls offer following configuration options:

• You can set a label to describe the control to users.

• You must set the value which resembles the following depending on the (sub)type. For legals this should either be the legal text itself (if limited) or an URL pointing to the text (recommended); for scopes this must be the scope value (OAuth 2.0).

• You must set the minimum score required in order to obtain or grant the control. Hence controls that provide more sensitive access can have a higher score, so more authentication factors will need to be passed.

Control requiredness is now configured through rules on clients.

The following options are only available for scopes:

• You can choose whether a consent is required when an account wants to grant it to a client. In general you want consent to be given, but sometimes certain scopes are implied and would not require explicit consent. In case you don't like to use consent management you can use this flag to disable consent.

• You can choose whether a permission is required in order for an account to use it. If you like to provide everyone access to a control you can uncheck this option, so no individual permissions have to be provided. For example admin scopes will usually require permission.

Legal controls are automatically configured as following:

• consent is required

• permission is not required

Control settings in the Tenant Admin UI