Skip to content

Commit aedefa6

Browse files
committed
Document authorization-scopes.json
Signed-off-by: Marko Strukelj <marko.strukelj@gmail.com>
1 parent 452cc8e commit aedefa6

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

examples/README-authz.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,10 @@ The possible resource types mirror the [Kafka authorization model](https://kafka
100100
Under `Authorization Scopes` we can see a list of all the possible actions (Kafka permissions) that can be granted on resources of different types.
101101
It requires some understanding of [Kafka's permissions model](https://kafka.apache.org/documentation/#resources_in_kafka) to know which of these make sense with which resource type (Topic, Group, Cluster, ...).
102102
This list mirrors Kafka permissions and should be the same for any deployment.
103-
There is a `authorization-scopes.json` file that can be imported so that these don't have to be manually entered for every new security realm.
103+
104+
There is an [authorization-scopes.json](../oauth-keycloak-authorizer/etc/authorization-scopes.json) file containing the authorization scopes that can be imported, so that they don't have to be manually entered for every new `Authorization Services` enabled client.
105+
In order to import `authorization-scopes.json` into a new client, first make sure the new client is `Authorization Enabled` and saved. Then, click on the `Authorization` tab and use the `Import` to import the file. Afterwards, if you select the `Authorization Scopes` you will see the loaded scopes.
106+
For this example the authorization scopes have already been imported as part of the realm import.
104107

105108
Under the `Policies` sub-tab there are filters that match sets of users.
106109
Users can be explicitly listed, or they can be matched based on the Roles, or Groups they are assigned.

0 commit comments

Comments
 (0)