"The market was screaming for a standard client protocol" in 1999, LDAP co-inventor Tim Howes told Network World in 2002.
X.500 didn’t have it. In addition, X.500, developed in the 1980s with input from telecom firms, required an OSI stack and an X.500 Server.
To go with the client protocol, LDAP Directory Servers soon popped up that had vestiges of X.500 still lurking in their depths. But like villagers in the comedy classic “Monty Python and the Holy Grail,” X.500 is not dead yet.
Some of its supporting protocols remain important directory security constructs, namely the X.509 authentication framework that is the cornerstone of PKI-based certificates. And LDAP has had its own evolutionary issues. LDAPv3, the last iteration of the protocol, lacks widely adopted access control and back-end integration extensions, namely replication, that have kept the protocol largely behind the firewall.
More Information#There might be more information for this subject on one of the following:
- Active Directory Service Interfaces
- Binary Encoding Option
- Cooperation for Open Systems Interconnection Networking in Europe
- DN Syntax
- Directory Access Protocol
- Directory Information Tree
- Directory System Agent
- Directory User Agent
- Distinguished Names
- Glossary Of LDAP And Directory Terminology
- History of LDAP
- Isode Limited
- Kim Cameron
- LDAP Directory Information Models
- Lightweight Directory Access Protocol (LDAP) entryUUID Operational Attribute
- Public Key Infrastructure
- RFC 2079
- The COSINE and Internet X.500 Schema