Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions admin_manual/configuration_user/user_auth_ldap.rst
Original file line number Diff line number Diff line change
Expand Up @@ -392,6 +392,21 @@ Group Member association:

* Example: *uniquemember*

.. warning::
Matching a user's ``gidNumber`` to a group's ``gidNumber`` also makes
Nextcloud treat that user as a member of the group. This is the POSIX
primary-group mechanism. It applies **in addition to** (and independently
of) whatever you configure here — for example ``member``, ``memberUid``,
or ``uniqueMember``.

So after you remove a user from an LDAP group via the usual membership
attribute, they may still appear as a member in the web UI and in
``occ`` output while their ``gidNumber`` still matches the group's. The
same idea applies to Active Directory ``primaryGroupID``. The attribute
name used for the user-side value is configurable as ``ldapGidNumber``
(default ``gidNumber``) via the LDAP configuration API / ``occ``, but it
is not exposed in the admin UI.

Nested groups:
Enable group member retrieval from sub groups.

Expand Down