LDAP Server
DPOD needs details about the LDAP server so it can query the LDAP user registry.
Please make sure you have the following details:
- LDAP server(s) IP address(es) (up to 2 IP addresses may be configured - a primary IP address and an alternate one)
- LDAP server port(s) (e.g. 389 or 3268 if using Global Catalog in AD)
- Whether LDAP referrals should be followed or ignored (usually ignored for better performance)
- A user distinguished name (DN) and its password which is used to connect to the LDAP server and can perform queries (e.g. "cn=LDAP Query User,ou=people,dc=example,dc=org")
LDAP Users
In order to authenticate users, DPOD needs to know what LDAP queries to perform in order to verify usernames and passwords.
The best way to discover it is to have a look at a user entry within the LDAP server using an LDAP browsing software compatible with your LDAP server.
Please make sure you have the following details:
- User base entry - the location of user entries in the LDAP tree (e.g. ou=people,dc=example,dc=org). Specific locations have better performance than global ones.
- Whether user entries should be queried in the entire sub-tree of the user base entry (usually true)
- User search query - the query to perform in order to find a user entry based on the login username.
Usually the user search query combines 2 conditions: First filter the entries based on "objectClass" attribute and then filter the entries based on the login username.
Usually user entries may be identified by an "objectClass" of "person", "organizationalPerson" or "inetOrgPerson".
The user entry attribute that contains the login username is usually "uid", "sAMAccountName" or "cn".
An example of a user search query: (&(objectClass=person)(sAMAccountName={0}))
Scenario A - Define Roles as attributes on the user directory entry
...