LDAP (Lightweight Directory Access Protocol) is how applications talk to a directory such as Active Directory — to authenticate users and look up group membership.
LDAP: Directory Access
The protocol applications use to query Active Directory.
Tap or hover a part to learn more.
Directory query protocol.
Lightweight Directory Access Protocol is the standard protocol for reading and writing directory data. Active Directory is queried over LDAP (port 389, or 636 for LDAPS). LDAP is the language; AD is one directory that speaks it.
Check your understanding
1. Which port does secure LDAP (LDAPS) use?
2. What does a Distinguished Name (DN) describe?
Keep learning
LDAP vs Active Directory
LDAP is the protocol (the language); Active Directory is a directory that speaks it. Queries run on port 389, or 636 for secure LDAPS.
Distinguished Names
Every object has a Distinguished Name (DN) describing its exact position in the tree, e.g. CN=Jane Doe,OU=Sales,DC=corp,DC=example,DC=com, built from Relative DNs (CN, OU, DC).
Binds and searches
A client binds to authenticate before querying. A simple bind must run over LDAPS so credentials aren't sent in clear text; SASL binds use stronger mechanisms like Kerberos. Applications then run search filters such as (&(objectClass=user)(department=IT)) to find objects — the backbone of directory-integrated logins.
This builds on Active Directory and is common ground for Security+ and application-integration work.
