keycloak-scim/authorization_services/topics/service-client-api.adoc

153 lines
5.3 KiB
Text
Raw Normal View History

2016-11-29 15:30:53 +00:00
[[_service_client_api]]
= Authorization Client Java API
2016-06-05 22:17:31 +00:00
2017-04-25 22:52:57 +00:00
Depending on your requirements, a resource server should be able to manage resources remotely or even check for permissions programmatically.
2017-08-28 12:50:14 +00:00
If you are using Java, you can access the {project_name} Authorization Services using the Authorization Client API.
2017-04-25 22:52:57 +00:00
It is targeted for resource servers that want to access the different APIs provided by the server such as the Protection, Authorization and Entitlement APIs.
2016-06-05 22:17:31 +00:00
== Maven Dependency
2016-06-05 22:17:31 +00:00
```xml
<dependencies>
<dependency>
<groupId>org.keycloak</groupId>
<artifactId>keycloak-authz-client</artifactId>
<version>${KEYCLOAK_VERSION}</version>
</dependency>
</dependencies>
```
== Configuration
2016-06-05 22:17:31 +00:00
2017-04-25 22:52:57 +00:00
The client configuration is defined in a ``keycloak.json`` file as follows:
2016-06-05 22:17:31 +00:00
```json
{
"realm": "hello-world-authz",
"auth-server-url" : "http://localhost:8080/auth",
"resource" : "hello-world-authz-service",
"credentials": {
"secret": "secret"
2016-06-05 22:17:31 +00:00
}
}
```
* *realm* (required)
2016-06-05 22:17:31 +00:00
+
The name of the realm.
* *auth-server-url* (required)
2016-06-05 22:17:31 +00:00
+
2017-08-28 12:50:14 +00:00
The base URL of the {project_name} server. All other {project_name} pages and REST service endpoints are derived from this. It is usually in the form https://host:port/auth.
* *resource* (required)
2016-06-05 22:17:31 +00:00
+
The client-id of the application. Each application has a client-id that is used to identify the application.
* *credentials* (required)
2018-01-23 03:14:17 +00:00
+
2017-04-25 22:52:57 +00:00
Specifies the credentials of the application. This is an object notation where the key is the credential type and the value is the value of the credential type.
The configuration file is usually located in your application's classpath, the default location from where the client is going to try to find a ```keycloak.json``` file.
== Creating the Authorization Client
2017-04-25 22:52:57 +00:00
Considering you have a ```keycloak.json``` file in your classpath, you can create a new ```AuthzClient``` instance as follows:
```java
// create a new instance based on the configuration defined in a keycloak.json located in your classpath
AuthzClient authzClient = AuthzClient.create();
```
2016-06-05 22:17:31 +00:00
== Obtaining User Entitlements
2016-06-05 22:17:31 +00:00
Here is an example illustrating how to obtain user entitlements:
2016-06-05 22:17:31 +00:00
```java
// create a new instance based on the configuration defined in keycloak-authz.json
2016-06-05 22:17:31 +00:00
AuthzClient authzClient = AuthzClient.create();
// obtain an Entitlement API Token to get access to the Entitlement API.
// this token is an access token issued to a client on behalf of an user
2017-04-25 22:52:57 +00:00
// with a uma_authorization scope
2016-06-05 22:17:31 +00:00
String eat = getEntitlementAPIToken(authzClient);
// send the entitlement request to the server to
// obtain an RPT with all permissions granted to the user
2017-04-25 22:52:57 +00:00
EntitlementResponse response = authzClient.entitlement(eat).getAll("hello-world-authz-service");
2016-06-05 22:17:31 +00:00
String rpt = response.getRpt();
// now you can use the RPT to access protected resources on the resource server
```
Here is an example illustrating how to obtain user entitlements for a set of one or more resources:
2016-06-05 22:17:31 +00:00
```java
// create a new instance based on the configuration defined in keycloak-authz.json
2016-06-05 22:17:31 +00:00
AuthzClient authzClient = AuthzClient.create();
// obtain an Entitlement API Token to get access to the Entitlement API.
// this token is an access token issued to a client on behalf of an user
2017-04-25 22:52:57 +00:00
// with a uma_authorization scope
2016-06-05 22:17:31 +00:00
String eat = getEntitlementAPIToken(authzClient);
// create an entitlement request
EntitlementRequest request = new EntitlementRequest();
PermissionRequest permission = new PermissionRequest();
permission.setResourceSetName("Hello World Resource");
request.addPermission(permission);
// send the entitlement request to the server to obtain an RPT
// with all permissions granted to the user
2017-04-25 22:52:57 +00:00
EntitlementResponse response = authzClient.entitlement(eat).get("hello-world-authz-service", request);
2016-06-05 22:17:31 +00:00
String rpt = response.getRpt();
2017-04-25 22:52:57 +00:00
// now you can use the RPT to access protected resources on the resource server
2016-06-05 22:17:31 +00:00
```
== Creating a Resource Using the Protection API
2016-06-05 22:17:31 +00:00
```java
// create a new instance based on the configuration defined in keycloak-authz.json
2016-06-05 22:17:31 +00:00
AuthzClient authzClient = AuthzClient.create();
// create a new resource representation with the information we want
ResourceRepresentation newResource = new ResourceRepresentation();
newResource.setName("New Resource");
newResource.setType("urn:hello-world-authz:resources:example");
newResource.addScope(new ScopeRepresentation("urn:hello-world-authz:scopes:view"));
ProtectedResource resourceClient = authzClient.protection().resource();
2017-04-25 22:52:57 +00:00
Set<String> existingResource = resourceClient.findByFilter("name=" + newResource.getName());
if (!existingResource.isEmpty()) {
resourceClient.delete(existingResource.iterator().next());
}
2016-06-05 22:17:31 +00:00
// create the resource on the server
RegistrationResponse response = resourceClient.create(newResource);
String resourceId = response.getId();
// query the resource using its newly generated id
ResourceRepresentation resource = resourceClient.findById(resourceId).getResourceDescription();
2017-04-25 22:52:57 +00:00
```
== Introspecting a RPT
2017-04-25 22:52:57 +00:00
```java
AuthzClient authzClient = AuthzClient.create();
String rpt = getRequestingPartyToken(authzClient);
TokenIntrospectionResponse requestingPartyToken = authzClient.protection().introspectRequestingPartyToken(rpt);
if (requestingPartyToken.getActive()) {
for (Permission granted : requestingPartyToken.getPermissions()) {
// iterate over the granted permissions
}
}
```