Active Directory (AD) is Microsoft's directory service, and it's the most common LDAP implementation you'll encounter in enterprise environments. If your organization runs Windows domains, AD is almost certainly the directory behind logins, email addresses, and group-based permissions.
Active Directory speaks standard LDAP — everything you learned in Getting Started (DNs, entries, binds, searches, filters) applies directly. AD also layers on Windows-specific protocols (Kerberos for authentication, DNS for service discovery, replication between domain controllers), but none of that is required to use AD as an LDAP directory from application code.
Note
Everything in Node.js works against Active Directory unchanged. This section covers the parts that are specific to AD: its base DN structure, its attribute names, and its authentication error codes.
A few things consistently trip people up when moving from generic LDAP knowledge to Active Directory specifically:
- The base DN is derived from the DNS domain name, not chosen freely — see LDAP in Active Directory.
- Attribute names differ from other directories in places —
sAMAccountNameinstead ofuid,userAccountControlinstead of a simple disabled flag. - Bind failures carry rich, AD-specific detail in an extended error string, not just a bare LDAP result code — see Authentication in Active Directory.
- LDAP in Active Directory — domain-to-DN mapping and connection basics.
- Users — how AD models user accounts.
- Groups — AD-specific group types and nesting.
- Common attributes — a reference table of frequently used AD attributes.
- Authentication — decoding AD's extended bind error codes.
Start with LDAP in Active Directory.