The server, in contrast, can speak only LDAP or use other methods to transmit data. For example, you could have an email program, address book, or printer browser as your client. LDAP doesn’t specify how programs operate on either the server or client side. As a protocol, LDAP only defines the “language” that clients can use to communicate with the servers (and that servers can use to communicate to servers). You can then use different applications or services such as Jenkins, Kubernetes or Docker to validate an AD network’s credentials.

In this regard, LDAP stores usernames and passwords. The most common application of LDAP is authenticating users to an AD network. But you can also find its applications in other directory services such as Red Hat Directory Servers, Open LDAP, and IBM Security Directory Server. LDAP is the core protocol used in Microsoft’s Active Directory. However, unlike X.500-based directories that run on the open systems interconnection (OSI) model, LDAP runs on the transmission control protocol/internet protocol (TCP/IP) to transfer services. LDAP is a lightweight protocol for accessing and managing directory services, particularly X.500-based directory services. Understanding the differences between LDAP and AD can help you protect your resources from critical security issues.

But what’s the difference between the two? LDAP is an open, vendor-agnostic, cross-platform protocol that works with multiple directory services, including AD.ĪD, in contrast, is Microsoft’s proprietary directory service that organizes various IT assets like computers and users. Lightweight Directory Access Protocol (LDAP) and Active Directory (AD) are at the core of any company’s security.

Azure active directory domain services