From 03d156a2d983155b89a1be34d62a2088dd93fc71 Mon Sep 17 00:00:00 2001 From: djeclemen Date: Tue, 30 Jul 2024 13:57:58 +0200 Subject: [PATCH] website/integrations: fix Nextcloud scopes (#10688) Co-authored-by: Marc 'risson' Schmitt --- website/integrations/services/nextcloud/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/integrations/services/nextcloud/index.md b/website/integrations/services/nextcloud/index.md index 43ad940a1f..bff3c13d46 100644 --- a/website/integrations/services/nextcloud/index.md +++ b/website/integrations/services/nextcloud/index.md @@ -137,7 +137,7 @@ Add a new provider using the `+` button and set the following values: :::tip If you are running both your authentik and Nextcloud instances behind a reverse proxy, you can go ahead and use your internal FQDN here (i.e. `http://authentik.local`, however, note that if you do so there is [extra configuration required](#extra-configuration-when-running-behind-a-reverse-proxy)). ::: -- Scope: `email`, `profile` (you can safely omit `openid` if you prefer) +- Scope: `email profile` (you can safely omit `openid` if you prefer) - Attribute mappings: - User ID mapping: sub (or `user_id` if you need to connect to an already existing Nextcloud user) - Display name mapping: name