[KEYCLOAK-8449] - Option to automatically map HTTP verbs to scopes when configuring the policy enforcer
This commit is contained in:
parent
36779b13b4
commit
371d5c1115
1 changed files with 12 additions and 2 deletions
|
@ -149,9 +149,19 @@ Specifies how policies are enforced.
|
|||
*** *claim-information-point*
|
||||
+
|
||||
Defines a set of one or more claims that must be resolved and pushed to the {project_name} server in order to make these claims available to policies. See <<_enforcer_claim_information_point, Claim Information Point>> for more details.
|
||||
+
|
||||
** *lazy-load-paths*
|
||||
+
|
||||
Specifies how the adapter should fetch the server for resources associated with paths in your application. If true, the policy
|
||||
Specifies how the adapter should fetch the server for resources associated with paths in your application. If *true*, the policy
|
||||
enforcer is going to fetch resources on-demand accordingly with the path being requested. This configuration is specially useful
|
||||
when you don't want to fetch all resources from the server during deployment (in case you have provided no `paths`) or in case
|
||||
you have defined only a sub set of `paths` and want to fetch others on-demand.
|
||||
+
|
||||
** *http-method-as-scope*
|
||||
+
|
||||
Specifies how scopes should be mapped to HTTP methods. If set to *true*, the policy enforcer will use the HTTP method from the current request to
|
||||
check whether or not access should be granted. When enabled, make sure your resources in {project_name} are associated with scopes representing each HTTP method you are protecting.
|
||||
+
|
||||
** *claim-information-point*
|
||||
+
|
||||
Defines a set of one or more *global* claims that must be resolved and pushed to the {project_name} server in order to make these claims available to policies. See <<_enforcer_claim_information_point, Claim Information Point>> for more details.
|
Loading…
Reference in a new issue