From e58f6d2d7a68d37035dba899f775578b5b8e5fb1 Mon Sep 17 00:00:00 2001 From: Martin Date: Tue, 18 Apr 2023 15:26:19 +0200 Subject: [PATCH] [docs-only] Update graph readme (GDPR, link to admin docs) Referencing: https://github.com/owncloud/docs-ocis/pull/457 (Add user triggered GDPR Report) Linking to the ocis admin documentation because we have more explainaition, images and an example json. --- services/graph/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/services/graph/README.md b/services/graph/README.md index 6813c2f48..6cfa65fe2 100644 --- a/services/graph/README.md +++ b/services/graph/README.md @@ -42,6 +42,8 @@ If Keycloak is used for authentication, GDPR regulations require to add all pers * `OCIS_KEYCLOAK_USER_REALM` - The realm the oCIS users are defined in. * `OCIS_KEYCLOAK_INSECURE_SKIP_VERIFY` - If set to true, the TLS certificate of the keycloak instance is not verified. +For more details see the [User-Triggered GDPR Report](https://doc.owncloud.com/ocis/next/deployment/gdpr/gdpr.html) in the ocis admin documentation. + ### Keycloak Client Configuration The client that is used to authenticate with keycloak has to be able to list users and get the credential data. To do this, the following roles have to be assigned to the client and they have to be about the realm that contains the oCIS users: