From 31471df033cd5124602a4d1cc4643a060d766e22 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rn=20Friedrich=20Dreyer?= Date: Fri, 24 Mar 2023 12:43:53 +0100 Subject: [PATCH] fix markdown --- services/invitations/README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/services/invitations/README.md b/services/invitations/README.md index a40ff2483..ea1596a73 100644 --- a/services/invitations/README.md +++ b/services/invitations/README.md @@ -6,12 +6,10 @@ Users invited via this Invitation Manager (libre graph API) will have `userType= The corresponding CS3 API [user types](https://cs3org.github.io/cs3apis/#cs3.identity.user.v1beta1.UserType) used to reperesent this are: `USER_TYPE_GUEST` and `USER_TYPE_PRIMARY`. - ## Provisioning backends When oCIS is used for user management the users are created using the `/graph/v1.0/users` endpoint. For larger deployments the keycloak admin API can be used to provision users. We might even make the endpoint, credentials and body configurable using templates. - ## Bridging provisioning delay When a guest account has to be provisioned in an external user management there might be a delay between creating the user and it being available in the local ocis system. In the first iteration the invitations service will only keep track of invites in memory. This list could be persisted in future iterations.