Jump to content

Lightweight Directory Access Protocol

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 172.213.172.246 (talk) at 22:32, 9 October 2005 (→External links). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

In computer networking, the Lightweight Directory Access Protocol, or LDAP, is a standardized networking protocol designed for querying and modifying directory services.

Origin and influences

The IETF designed and specified LDAP as a better way to make use of X.500 directories - having found the original Directory Access Protocol (DAP) too complex for simple internet clients to use. LDAP defines a relatively simple protocol for updating and searching directories running over TCP/IP.

The protocol was authored by Tim Howes of Netscape, Steve Kille of ISODE and Mark Wahl of Critical Angle Inc.

LDAP has influenced subsequent Internet protocols, including later versions of X.500, Directory Services Markup Language (DSML), Service Provisioning Markup Language (SPML) and the Service Location Protocol.

LDAP directories

The common term "LDAP directory" can mislead. No specific type of directory is an "LDAP directory". One could reasonably use the term to describe any directory accessible using LDAP and which can identify objects in the directory with X.500 identifiers. Directories such as OpenLDAP and its predecessors from the University of Michigan, though primarily designed as native repositories optimized for access by LDAP rather than as a gateway to X.500 protocols as was provided in ISODE, are nevertheless no more "LDAP directories" than any other directory accessible by the LDAP protocol.

An LDAP directory entry consists of a collection of attributes and is referenced unambiguously with a name, called a distinguished name (DN). For example, a DN might be the value "cn=John Doe,ou=people,dc=wikipedia,dc=org". Each of the entry's attributes are defined as part of an object class and are grouped together into schemas; those schemas for representing individual people within organizations are termed white pages schema. Each entry in the database is associated with one or more of these object classes, which define whether an attribute is optional or mandatory, and what type of information it stores. The attribute names are typically mnemonic strings, like "cn" for common name, or "mail" for e-mail address. The values depend on the type, and most non-binary values in LDAPv3 use UTF-8 string syntax. For example, a mail attribute might contain the value "[email protected]". A jpegPhoto attribute would contain a photograph in binary JPEG/JFIF format.

LDAP directory entries feature a hierarchical structure that reflects political, geographic, and/or organizational boundaries. In the original X.500 model, entries representing countries appear at the top of the tree; below them come entries representing states or national organizations. Typical LDAP deployments use DNS names for structuring the top levels of the hierarchy. Further below might appear entries representing people, organizational units, printers, documents, or just about anything else.

Supporting vendors

LDAP has gained wide support from vendors such as:

as well as in open source/free software implementations such as OpenLDAP and Fedora Directory Server. Also the Apache_HTTP_Server used as a proxy (by the module mod_proxy) supports LDAP.

RFCs

LDAP is defined by a series of Request for comments documents:

  • RFC 1777 - LDAPv2
  • RFC 1778 - LDAPv2 String Representation of Standard Attribute Syntaxes
  • RFC 2254 - String Representation of LDAP Search Filters
  • RFC 1823 - LDAP API (in C)
  • RFC 2247 - Use of DNS domains in distinguished names
  • RFC 2251 - LDAPv3: The specification of the LDAP on-the-wire protocol
  • RFC 2252 - LDAPv3: Attribute Syntax Definitions
  • RFC 2253 - LDAPv3: UTF-8 String Representation of Distinguished Names
  • RFC 2254 - LDAPv3: The String Representation of LDAP Search Filters
  • RFC 2255 - LDAPv3: The LDAP URL Format
  • RFC 2256 - LDAPv3: A Summary of the X.500(96) User Schema for use with LDAPv3
  • RFC 2829 - LDAPv3: Authentication Methods for LDAP
  • RFC 2830 - LDAPv3: Extension for Transport Layer Security
  • RFC 3377 - LDAPv3: Technical Specification
  • RFC 2307 - Using LDAP as a Network Information Service

References

This article is based on material taken from the Free On-line Dictionary of Computing prior to 1 November 2008 and incorporated under the "relicensing" terms of the GFDL, version 1.3 or later.

See also

Retrieved from "https://en.wikipedia.org/w/index.php?title=Lightweight_Directory_Access_Protocol&oldid=25155324"