The Lightweight Directory Access Protocol (LDAP) is a directory service protocol that runs on a layer above the TCP/IP stack. It provides a mechanism used to connect to, search, and modify Internet directories. The LDAP directory service is based on a client-server model.
Companies store usernames, passwords, email addresses, printer connections, and other static data within directories. LDAP is an open, vendor-neutral application protocol for accessing and maintaining data. LDAP can also tackle authentication, so users can sign on just once and access many different files on the server. LDAP is a protocol, so it doesn’t specify how directory programs.
As some examples, LDAP can be used to validate usernames and passwords with Docker, Jenkins, Kubernetes, Open VPN, and Linux Samba servers. LDAP single sign-on can also be used by system administrators to control access to an LDAP database.
To configure an LDAP connector, follow these steps:
- Provide a Connector Name: Choose a descriptive name for your LDAP connector. This name will help you identify the connector in your configuration.
- Choose OUTBOUND for the Connection Direction: Since LDAP operates based on a client-server model, you typically establish outbound connections from your system to the LDAP server.
- Choose LDAP for the Protocol: Select LDAP as the protocol for your connector. This protocol is specifically designed for accessing and maintaining data stored in LDAP directories.
- Optionally Provide a description: You can provide a brief description of the connector to help other users understand its purpose or functionality.
- Use the tick box to choose the Applications to which this connector applies.
Note: Host / Service Name (for docker) must always start with ldap://