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.
|Free Today: September Issue of Linux Journal (Retail value: $5.99)||Sep 27, 2016|
|nginx||Sep 27, 2016|
|Epiq Solutions' Sidekiq M.2||Sep 26, 2016|
|Nativ Disc||Sep 23, 2016|
|Android Browser Security--What You Haven't Been Told||Sep 22, 2016|
|The Many Paths to a Solution||Sep 21, 2016|
- Free Today: September Issue of Linux Journal (Retail value: $5.99)
- Android Browser Security--What You Haven't Been Told
- Readers' Choice Awards 2013
- Epiq Solutions' Sidekiq M.2
- The Many Paths to a Solution
- Nativ Disc
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Synopsys' Coverity
- Securing the Programmer
Pick up any e-commerce web or mobile app today, and you’ll be holding a mashup of interconnected applications and services from a variety of different providers. For instance, when you connect to Amazon’s e-commerce app, cookies, tags and pixels that are monitored by solutions like Exact Target, BazaarVoice, Bing, Shopzilla, Liveramp and Google Tag Manager track every action you take. You’re presented with special offers and coupons based on your viewing and buying patterns. If you find something you want for your birthday, a third party manages your wish list, which you can share through multiple social- media outlets or email to a friend. When you select something to buy, you find yourself presented with similar items as kind suggestions. And when you finally check out, you’re offered the ability to pay with promo codes, gifts cards, PayPal or a variety of credit cards.Get the Guide