Lightweight Directory Access Protocol
Subject: Computer and Technology noun /ˈlaɪtˌweɪt dɪˈrɛk.tər.i ˈæk.sɛs ˈproʊ.təˌkɔːl/ 1 definition
- computer-networking
- network-protocols
- directory-services
- identity-management
-
Definition (noun)
Entry #166 · UpdatedThe Lightweight Directory Access Protocol (LDAP) is an open, vendor-neutral application-layer protocol used to query, authenticate against, and modify distributed directory information services over TCP/IP. Originally designed as a streamlined alternative to the OSI X.500 Directory Access Protocol, it models records—such as user accounts, groups, devices, and permissions—as attribute-based entries arranged in a hierarchical Directory Information Tree (DIT), where each entry is identified by a unique Distinguished Name (DN). Unlike relational databases built for complex joins and high-volume transactions, LDAP serves specifically as a communication standard optimized for fast, read-heavy lookups and centralized identity management.
Common Forms
Plaintext LDAP: Runs unencrypted over TCP port 389 (
ldap://) and is typically restricted to isolated test environments or legacy integrations because credentials and queries travel in clear text.LDAP with StartTLS: Initiates a standard TCP connection on port 389 and issues a
StartTLSextended operation to upgrade the session to TLS encryption before transmitting credentials or sensitive directory data.LDAPS (LDAP over TLS): Wraps the entire LDAP session in an implicit TLS tunnel on TCP port 636 (
ldaps://) from the initial handshake, providing end-to-end transport encryption widely required by enterprise identity clients.LDAPI (LDAP over IPC): Routes LDAP protocol messages across local Unix domain sockets (
ldapi://) rather than TCP/IP, allowing local tools and services to authenticate and administer a directory server using operating-system socket permissions without exposing a network port.
Example
When an engineer logs into an internal web portal, the application opens an LDAPS connection on port 636 to
dir.example.comand binds asuid=mchen,ou=Engineering,dc=example,dc=comto verify their password. Once authenticated, it searches the directory tree formemberOfattributes to confirm group membership before issuing a session token.