LDAP Series Part III - The Historical Secrets

The origins of LDAP begin with the International Telecommunication Union (ITU) based in Geneva. ITU began setting email standards which required a directory of names (and other information) that could be accessed across networks in a hierarchical fashion not dissimilar to DNS. The result of their work resulted in the X.500 series of standards which defined DAP (Directory Access Protocol), the protocol for accessing a networked directory service.

Tim Howes, Steve Kille and Wengyik Yeong saw a better way to achieve the aims of ITU and published a proposal entitled X.500 Lightweight Directory Access Protocol in RFC 1487 during July 1993. Their abstract read as follows:

The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the Directory, and is intended to be a complement to the DAP itself.

Tim Howes of the University of Michigan led the development of LDAP supported by the National Science Foundation. From 1993 to 1997, the Internet Engineering Task Force (IETF) published 13 RFCs related to LDAP and dozens since. In essence, the University of Michigan invented and created LDAP. Two open source projects resulted from the work at the University of Michigan – OpenLDAP and the Fedora Directory Server.

On April 22, 1996, in a press release, the University of Michigan announced that "Netscape (would) incorporate Lightweight Directory Access Protocol (LDAP) directory service technology developed at the U-M into its World-Wide Web software." The University felt they had taken "a giant step toward having (a) global directory service on the Internet."

Netscape and the University partnered to create the Netscape Directory Server (NDS), which became the leading LDAP application in commercial use. Interestingly enough, Red Hat purchased NDS from AOL and open sourced its code. That resulted in delivery of Fedora Directory Server (FDS) to the Linux community.

The OpenLDAP Project was started in 1998 by Kurt Zeilenga. The project started by cloning the LDAP source code from the University Of Michigan. When attempting to access the original LDAP project, the page redirects you to the OpenLDAP project.

In essence, one could speculate that the OpenLDAP project became the successor of the University of Michigan project.

Subsequent Internet protocols have their origins in LDAP including the XML Enabled Directory (XED), Directory Services Markup Language (DSML), the Service Location Protocol (SLP) and the Service Provisioning Markup Language (SPML).

Of course, this short discussion requires mention of one other subsequent development - Active Directory (AD). Redmond utilized LDAP protocols to create AD, which demonstrates the remarkable potential of the founders' (Tim Howes, Steve Kille and Wengyik Yeong) work, which began back in 1993.

If you haven't delved into AD, you owe it to yourself to do so. The Linux community could use the AD blueprint to manage enterprises. That could extend the historical discussion of LDAP even further.

______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

LDAP begin with the International Telecommunication Union

china's picture

I think recently linux more intresting directions and all works make that more convient.

Don't touch Active Directory, let alone learn something!

Gavin Henry's picture

AD is all wrong and some of it isn't even standards based. Just keep using it for your Windows Domain Authentications and leave the real Directory servers to it ;-)
Gavin.

History of LDAP is missing...

Richard Lewis's picture

The history of LDAP is missing something unless the contributions of Novell and their legendary NDS are recognized. Ahead of the curve in it's day and which subsequently became an LDAP v3 implementation that runs on NetWare, Linux, Solaris, Windoze, etc...surely a conversation starter!

The Historical Secrets

sharkscott's picture

I love history..especially when its related to OSS. Hope all is well.

White Paper
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions