Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 38 ยท Getting Started

LDAP History, Standards and Versions

Trace LDAP from X.500 and DAP to LDAPv3, learn which RFCs define it, and see how OpenLDAP, 389 DS and Active Directory implement the standard.

LDAP did not appear from nowhere. It was created to make an older, heavier directory standard usable on ordinary networks. Knowing that story explains many odd details you will meet later: why names look like cn=Alice,ou=People,dc=example,dc=com, why the word "Lightweight" is in the name, and why every server supports "LDAP version 3".

In this lesson you will walk through the history, learn the standards that define the protocol today, and see how real products relate to them. You will also build a small lookup table you can reuse when you read RFC numbers in documentation.

From X.500 to LDAP

In the 1980s the telecommunications standards bodies (ITU-T and ISO) defined X.500, a grand design for a global directory: a worldwide tree of countries, organizations and people. X.500 clients talked to servers with the Directory Access Protocol (DAP). DAP ran on the full OSI network stack, which was complex and demanded a lot of memory and CPU. Desktop machines of the early 1990s struggled with it, and most organizations ran TCP/IP, not OSI.

At the University of Michigan in 1993, Tim Howes and colleagues designed a lightweight alternative. LDAP kept the X.500 data model (entries, attributes, a tree of names) but:

  • ran directly over TCP/IP instead of the OSI stack,
  • simplified the operations and the encoding of data,
  • used plain strings for many values instead of heavy binary structures.

Soon University of Michigan released a standalone LDAP server, which later grew into OpenLDAP. Netscape built a commercial server from the same code base, which is an ancestor of today's 389 Directory Server. In 1996 Microsoft announced it would build its own directory around LDAP, which shipped in Windows 2000 as Active Directory.

A short timeline

1988 X.500 Global directory, heavy DAP protocol.
1993 LDAP Lightweight gateway to X.500 over TCP.
1997 LDAPv3 Extensible, SASL, referrals.
2000 AD Active Directory ships with Windows 2000.

The protocol is old, stable and everywhere

1 / 2

LDAP versions

There were three protocol versions:

  • LDAPv1 and LDAPv2 (1993 to 1995): early versions, never widely standardized. LDAPv2 (RFC 1777) was retired in 2003 (RFC 3494).
  • LDAPv3 (RFC 2251, December 1997; restructured in 2006): the version everyone uses. It added extensibility through controls and extended operations, strong authentication with SASL, UTF-8 for all text, referrals between servers and a self-describing schema that clients can read.

When you configure a client you will sometimes see "protocol version 3". You should always choose 3. Version 2 clients are a legacy curiosity.

The standards that define LDAP

Since 2006 the specification is split into a set of RFCs known as the LDAP Technical Specification Road Map (RFC 4510). Learn the numbers once and you can find anything:

RFC Topic
4510 Road map: lists all the other documents
4511 The protocol itself: operations such as bind, search and modify
4512 Directory information models: entries, attributes, schema
4513 Authentication methods and security mechanisms
4514 String representation of distinguished names
4515 String representation of search filters
4516 LDAP URLs
4517 Syntaxes and matching rules
4518 Internationalized string preparation
4519 Schema for user applications (person, organizationalUnit, ...)
2849 LDIF, the text file format for entries and changes
4533 and others Extensions such as the content synchronization operation

You do not need to memorize these, but you will often search for "RFC 4515" when a filter confuses you.

Product implementations

All the major products implement LDAPv3 but differ in extras:

  • OpenLDAP (slapd): reference open-source server, configured mostly with LDIF stored inside the directory itself (cn=config).
  • 389 Directory Server and FreeIPA: Red Hat family, with a web UI and built-in Kerberos integration in FreeIPA.
  • Microsoft Active Directory Domain Services (AD DS): LDAP plus Kerberos plus DNS plus Group Policy. Its LDAP has important quirks, such as the sAMAccountName attribute and special matching rules for group nesting. You will learn them in the AD chapters.
  • Commercial servers: Oracle Unified Directory, IBM Security Directory, Ping Directory, and cloud services that expose an LDAP interface.

Because the protocol is shared, tools such as ldapsearch (from OpenLDAP) can query Active Directory too, and you can write one client library call that works against many servers.

A lookup helper (Python stand-in)

Let's turn the road map into a tiny tool. The first example looks up which RFC to read for a topic. The second uses a regular expression to find RFC numbers in a block of documentation text, a task you will really do when you read server manuals.

Python Which RFC explains it?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Python Extract RFC numbers from text

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Where Active Directory fits

Active Directory is not a different protocol. It is a directory server that implements LDAPv3 on port 389 (and LDAPS on 636) and adds its own conventions and services: Kerberos for authentication, DNS for locating servers, replication between domain controllers and Group Policy for managing computers. Microsoft's name for the LDAP-facing part in older documents is "ADSI" (Active Directory Service Interfaces), the programming layer Windows tools use.

You can think of the layers like this: LDAP is the language, the directory is the book of data, and Active Directory is a particular, very large library built around that language.

flowchart LR
    X500["X.500 DAP (1988)"] --> LDAP["LDAPv2 (1995)"]
    LDAP --> V3["LDAPv3 (1997, RFC 4510 set)"]
    V3 --> OL["OpenLDAP"]
    V3 --> DS["389 DS / FreeIPA"]
    V3 --> AD["Active Directory"]

Figure: LDAP descends from X.500 and is implemented by many servers.

When a vendor document says "standards compliant", check which LDAP RFCs it names. Active Directory deliberately deviates in a few places, so test your client against it rather than assuming OpenLDAP behavior.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why was LDAP called lightweight?

    LDAP removed the heavy OSI stack and simplified operations and encodings while keeping the X.500 model.
  2. 2. Which LDAP version should you configure today?

    LDAPv3 is the only version in active use. It added SASL, UTF-8, referrals and extensibility.
  3. 3. Which RFC defines the LDAP protocol operations such as bind and search?

    RFC 4511 is the protocol specification. RFC 2849 is LDIF, 4516 is LDAP URLs and 1777 was LDAPv2.
  4. 4. Active Directory relates to LDAP in which way?

    AD speaks LDAPv3 but is much more than a protocol: it is a full identity platform.

Summary

  • LDAP grew out of X.500's DAP as a lightweight, TCP-based way to reach directories.
  • LDAPv3 (1997, restructured by the RFC 4510 set in 2006) is the only version in use.
  • RFC 4511 is the protocol, 4512 the models, 4514 names, 4515 filters, 2849 LDIF.
  • OpenLDAP, 389 DS, FreeIPA and Active Directory all implement LDAPv3 with their own extras.
  • Active Directory = LDAP + Kerberos + DNS + replication + Group Policy.

Next: Active Directory Overview