Skip to content
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.

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

Force sync a ldap GROUP through command line or API #29727

Closed
maximelehericy opened this issue Nov 16, 2021 · 3 comments · Fixed by #39446
Closed

Force sync a ldap GROUP through command line or API #29727

maximelehericy opened this issue Nov 16, 2021 · 3 comments · Fixed by #39446
Assignees
Labels
4. to release Ready to be released and/or waiting for tests to finish enhancement feature: ldap feature: occ pending documentation This pull request needs an associated documentation update
Milestone

Comments

@maximelehericy
Copy link

maximelehericy commented Nov 16, 2021

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.

Is your feature request related to a problem? Please describe.
Today, an internal workflow allows a user to create a share for a group (groupfolder).
The group creation is done in our LDAP, and once the group created, a script triggers on Nextcloud side the creation of the share.
The existence of the group can be chacked via a occ ldap :search --group myGroup.
The group then exists on Nextcloud side, but isn't populated: we then set permissions on an empty group, users seeing the group only once the group content had been updated by the Cron job.

Describe the solution you'd like
A command occ ldap: group-update myGroup (or a group content feeding when a occ ldap :search --group command if the group wouldn't be referenced) would then make our process "immediate".

like occ ldap:check-group --fetch $GROUPNAME or occ ldap:check-group --update $GROUPID

Additional content
A similar demand exists to force the sync of a specific LDAP user : #27948

@maximelehericy maximelehericy added 0. Needs triage Pending check for reproducibility or if it fits our roadmap enhancement labels Nov 16, 2021
@AndyScherzinger AndyScherzinger added this to the Nextcloud 24 milestone Dec 23, 2021
@blizzz blizzz modified the milestones: Nextcloud 24, Nextcloud 25 Apr 21, 2022
@blizzz blizzz modified the milestones: Nextcloud 25, Nextcloud 26 Oct 19, 2022
@blizzz blizzz modified the milestones: Nextcloud 26, Nextcloud 27 Mar 9, 2023
@skjnldsv skjnldsv removed this from the Nextcloud 27.0.2 milestone Aug 8, 2023
@Constey
Copy link

Constey commented Aug 18, 2023

any news on this? could need it aswell :-)

@come-nc
Copy link
Contributor

come-nc commented Aug 28, 2023

any news on this? could need it aswell :-)

It was merged in master and will be in 28, I forgot to link the PR to the issue.
It will be a new ldap:check-group command inspired by the ldap:check-user command. Documentation is not there yet.

@come-nc come-nc self-assigned this Aug 28, 2023
@come-nc come-nc added 4. to release Ready to be released and/or waiting for tests to finish and removed 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Aug 28, 2023
@come-nc come-nc added this to the Nextcloud 28 milestone Aug 28, 2023
@AndyScherzinger AndyScherzinger added the pending documentation This pull request needs an associated documentation update label Nov 22, 2023
@blizzz blizzz modified the milestones: Nextcloud 28, Nextcloud 29 Nov 23, 2023
@joshtrichards
Copy link
Member

Fixed in #39446
Docs added in nextcloud/documentation#11079

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release Ready to be released and/or waiting for tests to finish enhancement feature: ldap feature: occ pending documentation This pull request needs an associated documentation update
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants