The Lightweight Directory Access Protocol (LDAP) is an open, vendor-neutral, industry standard application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network. Directory services play an important role in developing intranet and Internet applications by allowing the sharing of information about users, systems, networks, services, and applications throughout the network. As examples, directory services may provide any organized set of records, often with a hierarchical structure, such as a corporate email directory. Similarly, a telephone directory is a list of subscribers with an address and a phone number.
For troubleshooting tips see How to Authenticate User Manager via OpenLDAP
Directory Settings
- Secure Connection Type:
- None: No encryption
- Start TLS: TLS is negotiated over a plain TCP connection
- SSL: Secure Sockets Layer
- Host: The IP address of the AD server
- Port: TCP port if 389 for plain connections and 636 for SSL connections
- Bind DN or Username: A bind DN is an object that you bind to inside LDAP to give you permissions to do whatever you're trying to do. Some (many?) LDAP instances don't allow anonymous binds, or don't allow certain operations to be conducted with anonymous binds, so you must specify a bindDN to obtain an identity to perform that operation. Typically an administrator
- Password: Password of a user that is able to preform filter actions.
- Base DN: The base distinguished name. Usually in the format of DC=domain,DC=local. LDAP uses distinguished names to provide unique names to directory objects; every object in and LDAP server has an LDAP distinguished name. A distinguished name is a naming structure that consists of a string of the hierarchical components that make up the complete object.
- Status: Upon submittal the status will be green if User Manager was able to connect or red with the error
...