From a23bac9d9b895d072397bc4e48a380382c7258e4 Mon Sep 17 00:00:00 2001 From: Unfaehig <38919962+Unfaehig@users.noreply.github.com> Date: Mon, 7 Apr 2025 20:13:41 +0200 Subject: [PATCH] website/integrations: nextcloud: add warning about admin lockout (#13782) * docs: add a danger warning in nextcloud integration If a user follwoing the guide for OpenID integration. They can lock out their Admin users, if used the customer profile scope and select the **use unique user ID** option. So a danger box was added to let people know that can happen and why Signed-off-by: Unfaehig <38919962+Unfaehig@users.noreply.github.com> * docs: website/integrations/services/nextcloud/index.mdx Co-authored-by: Dominic R Signed-off-by: Unfaehig <38919962+Unfaehig@users.noreply.github.com> * chore: nextcloud integration fix formating --------- Signed-off-by: Unfaehig <38919962+Unfaehig@users.noreply.github.com> Co-authored-by: Dominic R --- website/integrations/services/nextcloud/index.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/integrations/services/nextcloud/index.mdx b/website/integrations/services/nextcloud/index.mdx index 3c1c0df3d2..ad3c7d2c43 100644 --- a/website/integrations/services/nextcloud/index.mdx +++ b/website/integrations/services/nextcloud/index.mdx @@ -173,6 +173,10 @@ Depending on your Nextcloud configuration, you might need to use `https://nextcl To avoid a hashed Federated Cloud ID, deselect **Use unique user ID** and use `user_id` for the User ID mapping. ::: + :::danger + If you are using a custom profile scope and want administrators to be able to log in, ensure that **Use unique user ID** is deselected. Otherwise, this setting will remove Administrator users from the internal admin group and replace them with a hashed group ID named "admin", which lacks actual admin access rights. + ::: + 3. **Log in:** Once configured, single sign-on (SSO) login via authentik becomes available.