Enabling Authorization Services
To turn your OIDC Client Application into a resource server and enable fine-grained authorization, select Access type confidential and click the Authorization Enabled switch to ON then click Save.
A new Authorization tab is displayed for this client. Click the Authorization tab and a page similar to the following is displayed:
The Authorization tab contains additional sub-tabs covering the different steps that you must follow to actually protect your application’s resources. Each tab is covered separately by a specific topic in this documentation. But here is a quick description about each one:
General settings for your resource server. For more details about this page see the Resource Server Settings section.
From this page, you can manage your application’s resources.
From this page, you can manage scopes.
From this page, you can manage authorization policies and define the conditions that must be met to grant a permission.
From this page, you can manage the permissions for your protected resources and scopes by linking them with the policies you created.
From this page, you can simulate authorization requests and view the result of the evaluation of the permissions and authorization policies you have defined.
From this page, you can export the authorization settings to a JSON file.
Resource Server Settings
On the Resource Server Settings page, you can configure the policy enforcement mode, allow remote resource management, and export the authorization configuration settings.
Policy Enforcement Mode
Specifies how policies are enforced when processing authorization requests sent to the server.
(default mode) Requests are denied by default even when there is no policy associated with a given resource.
Requests are allowed even when there is no policy associated with a given resource.
Disables the evaluation of all policies and allows access to all resources.
This configurations changes how the policy evaluation engine decides whether or not a resource or scope should be granted based on the outcome from all evaluated permissions.
Affirmativemeans that at least one permission must evaluate to a positive decision in order grant access to a resource and its scopes.
Unanimousmeans that all permissions must evaluate to a positive decision in order for the final decision to be also positive. As an example, if two permissions for a same resource or scope are in conflict (one of them is granting access and the other is denying access), the permission to the resource or scope will be granted if the choosen strategy is
Affirmative. Otherwise, a single deny from any permission will also deny access to the resource or scope.
Remote Resource Management
Specifies whether resources can be managed remotely by the resource server. If false, resources can be managed only from the administration console.