
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
216
|
Chapter 7: Using LDAP for Authentication
information” may be different, a directory service must be highly flexible and cus-
tomizable: it’s therefore an inherently complex undertaking.
Directory-Services Protocols
X.500, CCIT’s protocol for directory services, was designed to provide large-scale
directory services for very large and complex organizations. Accordingly, X.500 is
itself a large and complex protocol, so much so that a “lightweight” version of it was
created: the Lightweight Directory Access Protocol (LDAP). LDAP, described in
RFCs 1777 and 2251, is essentially a subset of the X.500 protocol, and it’s been far
more widely implemented than X.500 itself.
X.500 and LDAP are open protocols, like TCP/IP: neither is a standalone product. A
protocol has to be implemented in some sort of software, such as a kernel module, a
server daemon, or a client program. Also like TCP/IP, not all implementations of
LDAP are alike, or even completely interoperable (without modification). The partic-
ular LDAP implementation we’ll cover here is OpenLDAP, but you should be aware
that other software products provide alternative implementations. These include
Netscape Directory Server, Sun ONE Directory Server, and even, in a limited way,
Microsoft Active Directory (in Windows 2000 Server).