Generated by GPT-5-mini| Lightweight Directory Access Protocol | |
|---|---|
| Name | Lightweight Directory Access Protocol |
| Acronym | LDAP |
| Developer | University of Michigan; Internet Engineering Task Force |
| Initial release | 1993 |
| Latest version | LDAPv3 (1997) |
| Type | Directory service protocol |
| License | Various (open standards) |
Lightweight Directory Access Protocol Lightweight Directory Access Protocol is an open protocol for accessing and managing directory information over an IP network. It originated as a streamlined alternative to heavyweight directory protocols and became an Internet standard widely used in enterprise identity systems, enterprise resource planning, cloud services, and network operating systems. LDAP interoperates with many Sun Microsystems products, Microsoft services, Red Hat distributions, and standards bodies such as the Internet Engineering Task Force and Organization for the Advancement of Structured Information Standards.
LDAP defines a client–server model for querying and modifying directory entries stored on directory servers such as OpenLDAP and Microsoft Active Directory. Common operations include Bind, Search, Compare, Add, Delete, Modify, and Unbind, performed over transport services like Transmission Control Protocol and optionally secured by Transport Layer Security. LDAP directories are used by applications including Apache HTTP Server, Samba, Postfix, Dovecot, and identity providers in Amazon Web Services, Google Cloud Platform, and Microsoft Azure. LDAP entries are organized in a hierarchical naming context influenced by systems like X.500 and directory-aware services such as Novell eDirectory.
LDAP emerged from directory efforts at the University of Michigan as a simpler alternative to the International Telecommunication Union and International Organization for Standardization standard X.500 Directory Access Protocol. Early work involved contributors from Tim Howes, Mark Smith and colleagues, and implementations such as the University of Michigan LDAP server influenced commercial offerings by Netscape and Sun Microsystems. The protocol was standardized through the Internet Engineering Task Force with a sequence of RFCs and influenced later directory-related standards from the World Wide Web Consortium and the Organization for the Advancement of Structured Information Standards.
LDAP specifies an application protocol operating over TCP/IP with message encoding defined using the Abstract Syntax Notation One rules, and presentation details aligned with BER encoding from the International Telecommunication Union standards. LDAPv3 introduced features such as referrals, extension mechanisms, and controls that integrate with authentication systems like Kerberos and with directory replication solutions pioneered by vendors including IBM and Oracle Corporation. Clients range from command-line tools like ldapsearch to libraries in Python (programming language), Java (programming language), C#, and implementations in Go (programming language) and Perl. LDAP servers implement replication, indexing, and access control features found in products like 389 Directory Server and Apache Directory Server.
LDAP directories store entries identified by Distinguished Names derived from attributes such as commonName, organizationName, and countryName, drawing on naming contexts used by the Domain Name System and by X.500. Schemas define objectClasses and attributeTypes; common schemas include inetOrgPerson, organizationalRole, and groupOfNames used by projects like FreeIPA and Keycloak. Schema extensibility enables integration with applications such as OpenVPN, Jenkins, GitLab, and Kubernetes via LDAP-backed authentication and authorization. Tools for schema management include editors in Red Hat management consoles and GUI utilities provided by Softerra and JXplorer.
Security for LDAP involves transport-layer encryption with Transport Layer Security, authentication methods including Simple Bind, SASL mechanisms, and integration with authentication frameworks like Kerberos and NTLM. Deployments often combine LDAP with multi-factor authentication from providers such as Duo Security, Okta, and Ping Identity. Threat mitigation references implementations of access control lists, password policy overlays, and logging compatible with SIEM solutions from Splunk, Elastic (company), and IBM QRadar. Standards for password hashing and secure storage borrow techniques used by OpenSSL and cryptographic libraries maintained by Mozilla.
LDAP has been implemented by open-source projects like OpenLDAP, 389 Directory Server, and Apache Directory Project and by commercial systems including Microsoft Active Directory, Oracle Internet Directory, and Novell eDirectory. Large organizations use LDAP for centralized authentication in environments managed with Red Hat Enterprise Linux, Ubuntu, and SUSE Linux Enterprise Server and for single sign-on with platforms such as Salesforce and ServiceNow. Cloud vendors provide managed directory services integrated with identity platforms from Amazon Web Services, Google Cloud Platform, and Microsoft Azure Active Directory Domain Services. LDAP is also embedded in networking equipment from Cisco Systems and Juniper Networks for user authentication and directory lookups.
LDAP has evolved through a series of RFCs published by the Internet Engineering Task Force, with extensions covering controls, paged results, virtual list views, and persistent searches used in synchronization solutions like Microsoft Identity Manager and Okta Universal Directory. Interoperability work involves schema mapping with SAML assertions from OASIS and with OAuth 2.0 flows specified by the IETF OAuth Working Group. The ecosystem continues to adapt with projects supporting SCIM standards from the IETF and integration efforts involving Grafana, Prometheus, and configuration management tools such as Ansible and Puppet.
Category:Internet protocols