From bf397732e72470edbbe1ae72139b5df36aff9c7d Mon Sep 17 00:00:00 2001 From: Ralf Haferkamp Date: Tue, 19 May 2026 08:31:24 +0200 Subject: [PATCH] docs(adr): Remove erroneous mention of kanidm Apparently kanidm does allow to set the client-id. --- docs/adr/0003-oidc-client-config-discovery.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/adr/0003-oidc-client-config-discovery.md b/docs/adr/0003-oidc-client-config-discovery.md index f1e07f006d..14cd348ffe 100644 --- a/docs/adr/0003-oidc-client-config-discovery.md +++ b/docs/adr/0003-oidc-client-config-discovery.md @@ -18,7 +18,7 @@ OpenCloud with various existing identity providers. For example: - Authentik basically creates a different issuer URL for each client. As OpenCloud can only work with a single issuer URL, all OpenCloud clients need to use the same client id to work with Authentik. -- Some IDPs (kanidm) are not able to work with user-supplied client ids. They generate +- Some IDPs are not able to work with user-supplied client ids. They generate client ids automatically and do not allow to specify them manually. - To make features like automatic role assignment work, clients need to request specific scopes, depending on which exact IDP is used.