Skip to content

website/integrations: change nextcloud scope name to avoid confusion #15050

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BeryJu merged 1 commit into from
Jun 16, 2025
Merged

website/integrations: change nextcloud scope name to avoid confusion #15050

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions website/integrations/services/nextcloud/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ If you want to control user storage and designate Nextcloud administrators, you
- **Create Scope Mapping**:

- **Name**: `Nextcloud Profile`
- **Scope name**: `profile`
- **Scope name**: `nextcloud`
- **Expression**:

```python
Expand Down Expand Up @@ -146,7 +146,7 @@ Depending on your Nextcloud configuration, you may need to use `https://nextclou
- **Client ID**: Client ID from authentik
- **Client secret**: Client secret from authentik
- **Discovery endpoint**: `https://authentik.company/application/o/<application_slug>/.well-known/openid-configuration`
- **Scope**: `email profile openid`
- **Scope**: `email nextcloud openid`
- Under **Attribute mappings**:

- **User ID mapping**: `sub` (or `user_id` for existing users)
Expand Down
Loading