keycloak-scim/authorization_services/topics/policy/evaluation-api.adoc

112 lines
3.6 KiB
Text
Raw Normal View History

2016-11-29 15:30:53 +00:00
[[_policy_evaluation_api]]
2016-12-02 15:25:43 +00:00
=== Policy Evaluation API
2017-08-28 12:50:14 +00:00
When writing rule-based policies using JavaScript or JBoss Drools, {project_name} provides an Evaluation API that provides useful information to help determine whether a permission should be granted.
This API consists of a few interfaces that provides you access to information such as:
2016-06-29 22:51:16 +00:00
* The permission being requested
* The identity that is requesting the permission, from which you can obtain claims/attributes
2016-06-29 22:51:16 +00:00
* Runtime environment and any other attribute associated with the execution context
The main interface is *org.keycloak.authorization.policy.evaluation.Evaluation*, which defines the following contract:
```java
public interface Evaluation {
/**
* Returns the {@link ResourcePermission} to be evaluated.
*
* @return the permission to be evaluated
*/
ResourcePermission getPermission();
/**
* Returns the {@link EvaluationContext}. Which provides access to the whole evaluation runtime context.
*
* @return the evaluation context
*/
EvaluationContext getContext();
/**
* Grants the requested permission to the caller.
*/
void grant();
/**
* Denies the requested permission.
*/
void deny();
}
```
2017-08-28 12:50:14 +00:00
When processing an authorization request, {project_name} creates an `Evaluation` instance before evaluating any policy. This instance is then passed to each policy to determine whether access is *GRANT* or *DENY*.
2016-06-29 22:51:16 +00:00
Policies determine this by invoking the `grant()` or `deny()` methods on an `Evaluation` instance. By default, the state of the `Evaluation` instance is denied, which means that your policies must explicitly invoke the `grant()` method to indicate to the policy evaluation engine that permission should be granted.
2016-06-05 22:17:31 +00:00
2017-09-05 07:49:24 +00:00
For more information about the Evaluation API see the {apidocs_link}[JavaDocs].
2017-04-04 19:10:19 +00:00
==== The Evaluation Context
2016-06-05 22:17:31 +00:00
The evaluation context provides useful information to policies during their evaluation.
```java
public interface EvaluationContext {
/**
* Returns the {@link Identity} that represents an entity (person or non-person) to which the permissions must be granted, or not.
*
* @return the identity to which the permissions must be granted, or not
*/
Identity getIdentity();
/**
* Returns all attributes within the current execution and runtime environment.
*
* @return the attributes within the current execution and runtime environment
*/
Attributes getAttributes();
}
```
From this interface, policies can obtain:
2016-06-29 22:51:16 +00:00
* The authenticated `Identity`
2016-06-05 22:17:31 +00:00
* Information about the execution context and runtime environment
The `Identity` is built based on the OAuth2 Access Token that was sent along with the authorization request, and this construct has access to all claims
extracted from the original token. For example, if you are using a _Protocol Mapper_ to include a custom claim in a OAuth2 Access Token you can also access this claim
from a policy and use it to build your conditions.
2016-06-29 22:51:16 +00:00
The `EvaluationContext` also gives you access to attributes related to both the execution and runtime environments. For now, there only a few built-in attributes.
2016-06-29 22:51:16 +00:00
.Execution and Runtime Attributes
|===
|Name |Description | Type
| kc.time.date_time
| Current date and time
| String. Format `MM/dd/yyyy hh:mm:ss`
| kc.client.network.ip_address
| IPv4 address of the client
| String
| kc.client.network.host
| Client's host name
| String
| kc.client.id
| The client id
| String
| kc.client.user_agent
| The value of the 'User-Agent' HTTP header
| String[]
| kc.realm.name
| The name of the realm
| String
|===