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.
Webinar: 8 Signs You’re Beyond Cron
On Demand NOW
Join Linux Journal and Pat Cameron, Director of Automation Technology at HelpSystems, as they discuss the eight primary advantages of moving beyond cron job scheduling. In this webinar, you’ll learn about integrating cron with an enterprise scheduler.View Now!
|June 2015 Issue of Linux Journal: Networking||Jun 01, 2015|
|June 2015 Video Preview||Jun 01, 2015|
|My Humble Little Game Collection||May 28, 2015|
|New Linux Based OS Brings Internet of Things Closer to Reality||May 27, 2015|
|Non-Linux FOSS: All the Bitcoin, None of the Bloat||May 26, 2015|
|Dr Hjkl on the Command Line||May 21, 2015|
- June 2015 Issue of Linux Journal: Networking
- New Linux Based OS Brings Internet of Things Closer to Reality
- Dr Hjkl on the Command Line
- Initializing and Managing Services in Linux: Past, Present and Future
- My Humble Little Game Collection
- Using Hiera with Puppet
- Gartner Dubs DivvyCloud Cool Cloud Management Vendor
- Infinite BusyBox with systemd
- Goodbye, Pi. Hello, C.H.I.P.
- Non-Linux FOSS: All the Bitcoin, None of the Bloat