Skip to content

docs(admin): warn that LDAP gidNumber keeps group membership - #15715

Open
whoalin1 wants to merge 2 commits into
nextcloud:masterfrom
whoalin1:docs-ldap-gidnumber-membership-caveat
Open

whoalin1 wants to merge 2 commits into
nextcloud:masterfrom
whoalin1:docs-ldap-gidnumber-membership-caveat

Conversation

@whoalin1

@whoalin1 whoalin1 commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Document the LDAP POSIX primary-group footgun: matching user/group gidNumber (or AD primaryGroupID) keeps the user in the Nextcloud group even after they are removed via the configured membership attribute.

  • Warning on the admin Group Member association field in user_auth_ldap.rst.
  • Clarifies the relation is independent of member / memberUid / uniqueMember.
  • Notes leftover UI/occ membership, that ldapGidNumber is configurable but not in the UI, and that ldap:show-remnants does not clear this secondary relation.

Closes #11148

Test plan

  • Sphinx build of the admin manual succeeds for user_auth_ldap.rst
  • New .. warning:: appears after Group Member association and before Nested groups
  • Mentions gidNumber, independence from assoc attr, AD primaryGroupID, ldapGidNumber, and that show-remnants is unrelated
  • No cleanup / API pages changed

AI disclosure

This PR was drafted with the help of AI coding assistants (Cursor agents / LLM-based tools), including the description. I am responsible for it and happy to rework anything that doesn't fit.

All commits carry an Assisted-by: Cursor:grok-4.7 trailer.

Assisted-by: Cursor:grok-4.7
Signed-off-by: whoalin1 <whoalin414@gmail.com>
@whoalin1
whoalin1 force-pushed the docs-ldap-gidnumber-membership-caveat branch from 54c1916 to ab6443f Compare October 9, 2026 14:12
Comment on lines +409 to +413

Prefer distinct ``gidNumber`` namespaces for users versus groups, or
change the user's ``gidNumber`` / ``primaryGroupID`` when membership
should end. ``ldap:show-remnants`` only lists deleted users and does not
clear this secondary relation.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Prefer distinct ``gidNumber`` namespaces for users versus groups, or
change the user's ``gidNumber`` / ``primaryGroupID`` when membership
should end. ``ldap:show-remnants`` only lists deleted users and does not
clear this secondary relation.

I do not understand this part and why it mentions show-remnants.
The rest of the changes look good.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @come-nc, I applied your suggestion and removed that paragraph in c17a053.

AI disclosure: this PR and reply were drafted with help from an AI assistant (Assisted-by trailer on the commits).

@github-actions

Copy link
Copy Markdown
Contributor

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

… note

Assisted-by: Cursor:grok-4.7
Signed-off-by: whoalin1 <whoalin414@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Admin] LDAP: user's attribute gidNumber is used for group relations

3 participants