Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Group base entryThe location of group entries in the LDAP tree. Specific locations have better performance than global ones.
e.g. "ou=groups,dc=example,dc=org"
Role query sub-treeWhether group entries should be queried in the entire sub-tree of the group base entry (usually true).
Nested groupsWhether group entries can be nested in each other (usually true).
Group search filterThe search filter to use in order to fetch the list of groups a user belongs to once a user has authenticated successfully.
Usually the group search filter combines 2 conditions: First filter the entries based on "objectClass" attribute and then filter the entries based on the authenticated user.
Usually group entries may be identified by an "objectClass" of "group" or "groupOfUniqueNames".
The group entry attribute that contains its members is usually "member" or "uniquemember".
e.g. "(&(objectClass=groupOfUniqueNames)(uniqueMember={1}))"
Group name attribute name

The attribute name at the group entry that contains the group name.
Group names are used to assign groups to Custom Roles defined in DPOD.
e.g. "cn"

Built-in Roles

For security reasons, authenticated users are assigned with built-in roles based on LDAP queries only.
This means, for example, that a user may be granted with Administrator privileges only if it is configured that way in the LDAP user repository.

...