nextcloud / nextcloud/scim_client
Add option to disable bulk operations for each server
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
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: master (33.0.0)
Is your feature request related to a problem? Please describe.
Now that bulk support is no longer required as of #109, it might be nice to have the option to not sync users/groups in bulk even if the server supports it.
Describe the solution you'd like
Add to each SCIM server a toggle that enables/disables the use of bulk operations for that server. That way, bulk operations are only used if it is enabled in both the app and the server.
Describe alternatives you've considered
This may not be completely necessary as a workaround would be to toggle bulk support in the SCIM server itself, but could be helpful in situations when bulk support cannot be disabled from the server side.
Additional context
(none)
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. Start by locating the SCIM server configuration and the code paths that choose bulk user or group operations; then trace how server settings are stored and exposed. Done means each server can independently enable or disable bulk operations, with bulk used only when both relevant settings allow it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100