Home > Articles

Lightweight Directory Access Protocol (LDAP)

This chapter is from the book


Lightweight Directory Access Protocol (LDAP) is the core communication and access protocol behind all major directory server products today, including Active Directory. LDAP was developed at the University of Michigan in the early 1990s. The first specification was submitted as RFC 1487 in 1993 and the most recent, LDAP v3, in 1997 as RFC 2252. LDAP is a protocol, but is also associated with an application programming interface (API), which is defined in the informational RFC 1823. Since LDAP is both a protocol and an API, there is much confusion over what LDAP does. The following sections clarify the nuances.

LDAP as a Protocol

As its name implies, LDAP was initially intended to be a lightweight protocol. LDAP was developed as an alternative to the x.500 Directory Access Protocol (DAP). DAP is based on the OSI model and as such incorporates many of the complexities and inefficiencies that come with OSI. The LDAP protocol defines the transport and format of messages between a client and an LDAP enabled server or gateway. Initially, LDAP was created to work over TCP, but later Connectionless LDAP (CLDAP) was defined in RFC 1789 to work over UDP for implementations that did not want to incur the overhead of TCP.

LDAP was designed to be simple yet extensible so additional features could be added later while maintaining backward compatibility. LDAP uses a mechanism called controls, which will be discussed later in the chapter, to define extensions to the protocol without actually modifying the protocol. Server-side sorting, paging, and tree delete are examples of enhancements that have been made to LDAP by the use of controls. New controls generally go through the RFC process to gain industry acceptance before implementation, but some vendors, such as Microsoft, have implemented their own controls for use specifically within their directory products. Appendix C covers the controls implemented in Active Directory.

LDAP provides read as well as write access to a directory. A typical directory, such as a phone book, is read much more frequently than it is written. For that reason, LDAP was optimized for reading rather than writing.

LDAP is based on the X.500 data model, which is highly extensible and can be dynamically manipulated. It is also hierarchical, unlike traditional databases, so relationships and dependencies among data can be easily modeled and controlled.

LDAP as an API

LDAP is associated with a C API defined in RFC 1823. This is very uncommon among protocol standards and is one reason why LDAP thrived early on. It is important to note that RFC 1823 is not a standard or proposed standard, but only informational. Other APIs that have been written do not conform to the C-style API. Some examples include the Perl-based Net::LDAP modules and the Java Naming and Directory Interface (JNDI), both of which are object-oriented.

Most LDAP APIs are composed of three primary groups of functions. Table 3.1 illustrates the grouping along with some of the C-style LDAP functions that are associated with them.

Table 3.1 Common LDAP Functions


C-Style LDAP Functions

Connecting, disconnecting, authenticating

ldap_connect(), ldap_open(), and ldap_bind(), ldap_unbind()

Searching and retrieving entries

ldap_search(), ldap_first_entry(), ldap_next_entry()

Manipulating entries

ldap_add, ldap_modify(), ldap_modrdn(), ldap_delete(), ldap_compare()

What LDAP Is Not

While LDAP is very good at some things, such as being very efficient for reading data and being more easily distributable than a database, some limitations have caused problems for implementers. The first warning for anyone new to LDAP is that an LDAP directory should not be treated like a database. There is no transactional capability within LDAP, which means it is not possible to roll back changes or to make a series of changes in a single transaction as in a traditional database. This makes LDAP directories a bad choice for systems that depend on transaction or order processing, such as bank and airline systems.

Lack of a standard replication mechanism is one of the biggest complaints from enterprise deployers of LDAP. Most LDAP vendors have been required to develop their own methodology to replicate data among LDAP servers. Many of the early LDAP servers are only capable of a single master architecture. That means one server is designated as the master and contains a writable copy of the directory contents, and the other servers are subordinate or secondary and have read-only copies. When the master server is updated, it replicates the change to the other subordinate servers. This model is much simpler and easier to maintain than a multimaster architecture, but it is also much more limiting especially for global deployments. Active Directory is one of the first directories to support true multimaster replication where any number of servers can be updated. However, having multimaster capabilities does not come without its pitfalls. As you will read in the Chapter 9, "Site Topology and Replication," Active Directory replication is one of the most labor-intensive and troublesome areas within Active Directory.

Synchronization of disparate directories is another issue for most companies because of the need to support multiple directories within the enterprise. Most directories available today perform only one of the major directory functions very well. For example, Netscape iPlanet is known for having the best enterprise or application directory, whereas Microsoft and Novell have the best network operating system (NOS) directories. Since many companies have more than one directory, there is a need to synchronize some of the data between them. Currently, there is no standard way to do this. Since a synchronization mechanism was not included in the LDAP specification, most LDAP vendors have been reluctant to work together to form a standard. As a result, there has been a proliferation of metadirectory products. Metadirectories facilitate the synchronization of data between disparate directories and databases based on business logic. The primary problem with implementing metadirectories is the complexity involved in configuring and maintaining the necessary business logic to keep the various databases and directories in sync.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020