nextcloud / nextcloud/documentation
[Admin] LDAP: user's attribute gidNumber is used for group relations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 628
- Forks
- 2.5k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 135
Description
If gidNumber from user entry matches gidNumber from group, user will also be considered as part of this group. Then after removing a user from LDAP group, and cleanup with ldap:show-remnants, user is still shown as a group member in web-interface and occ output.
Should be noted in documentation, as it may lead to raising a ticket from customers, who tries to remove users
Documentation source:
https://github.com/nextcloud/documentation/blob/master/admin_manual/configuration_user/user_auth_ldap_api.rst
or
https://github.com/nextcloud/documentation/blob/master/admin_manual/configuration_user/user_auth_ldap_cleanup.rst
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
Start with admin_manual/configuration_user/user_auth_ldap_api.rst and admin_manual/configuration_user/user_auth_ldap_cleanup.rst, focusing on LDAP group membership and cleanup behavior. Document that a matching gidNumber can make a user appear in a group even after removal, so the existing web-interface and occ output are understandable; the relevant documentation should clearly explain this behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100