nextcloud / nextcloud/user_oidc
Add a "exclude groups matching this regexp" below the "Group whitelist regex"
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 181
- Forks
- 60
- Avg merge
- 7h 34m
- Merged PRs (30d)
- 26
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using: 30.0.12
Is your feature request related to a problem? Please describe.
It's quite hard for non technical user to know how to write a "negative matching" regex, so if you want to synchronize ALL your groups BUT not a few of them, you have a hard time.
It would be a lot easier to have a second field, below the "Group whitelist regex" one, to setup "excluded groups regex".
eg:
Group whitelist regex: /.*/
Group exclusion regex: /^(admin|default-realm-role)$/
Describe the solution you'd like
below the "Group whitelist regex" field, you could add a
"Group exclusion regex" similar field, that would be checked, when non empty, to exclude the matching groups in the group mapping between the oidc identity provider and the Nextcloud
Describe alternatives you've considered
using negative regex works, but it's very difficult to explain to non-tech-savvy administratord of Nextcloud
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Locate the existing “Group whitelist regex” setting and the group-mapping path, then read how the whitelist is configured and applied. Add the requested exclusion setting and verify that matching groups are omitted while existing whitelist behavior remains intact, using the repository’s tests for this path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100