Repository navigation
Conversation
Assisted-by: Cursor:grok-4.7 Signed-off-by: whoalin1 <whoalin414@gmail.com>
54c1916 to
ab6443f
Compare
|
|
||
| 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. |
There was a problem hiding this comment.
| 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.
|
Hello there, 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>
Summary
Document the LDAP POSIX primary-group footgun: matching user/group
gidNumber(or ADprimaryGroupID) keeps the user in the Nextcloud group even after they are removed via the configured membership attribute.user_auth_ldap.rst.member/memberUid/uniqueMember.occmembership, thatldapGidNumberis configurable but not in the UI, and thatldap:show-remnantsdoes not clear this secondary relation.Closes #11148
Test plan
user_auth_ldap.rst.. warning::appears after Group Member association and before Nested groupsgidNumber, independence from assoc attr, ADprimaryGroupID,ldapGidNumber, and that show-remnants is unrelatedAI 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.7trailer.