You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Keycloak is responsible for handling the authentication with the standard OpenID Connect and manages user access with its Role Model.
19
-
* Keycloak is configured with a new custom extension :rocket:[keycloak-openfga-event-publisher](https://github.com/embesozzi/keycloak-openfga-event-publisher) which listens to the Keycloak events (User Role Assignment, Role to Role Assignment, etc), parses this event into an OpenFGA tuple based on the [Keycloak Authorization Schema](model.dsl) and publishes them to OpenFGA over HTTP.
19
+
* Keycloak is configured with a new custom extension ❤️: [keycloak-openfga-event-publisher](https://github.com/embesozzi/keycloak-openfga-event-publisher)
20
+
* Listens to the Keycloak events (User Role Assignment, Role to Role Assignment, etc).
21
+
* Parses this event into an OpenFGA tuple key based on the [Keycloak Authorization Schema](model.dsl).
22
+
* Publishes them to OpenFGA over HTTP using the [OpenFGA Java SDK](https://github.com/openfga/java-sdk).
20
23
* OpenFGA is responsible for applying fine-grained access control. The OpenFGA service answers authorization checks by determining whether a relationship exists between an object and a user.
21
24
* Other components
22
25
* Store Web Application is integrated with Keycloak by OpenID Connect
23
26
* Store API is protected by OAuth 2.0 and it utilizes the OpenFGA SDK for FGA
24
27
28
+
25
29
# How to install?
26
30
## Prerequisites
27
31
@@ -49,12 +53,12 @@ The following diagram illustrates the solution architecture of this workshop:
49
53
50
54
4. Access the following web UIs using URLs bellow via a web browser.
0 commit comments