2.4 Protocol Summary
The following tables provide a comprehensive list of the member protocols of the Active Directory system. Section 2.8 provides details about which protocols or protocol subsets are supported in the different modes of operation.
The protocols in the following table enable the core functionality of the Active Directory system, including access to the directory tree, replication, name translation, determination of group membership, and domain controller status. These protocols are supported by all directory servers in the Active Directory system, whether running in Active Directory Domain Services (AD DS) or Active Directory Lightweight Directory Services (AD LDS) mode.
Protocol name |
Description |
Short name |
---|---|---|
Active Directory extensions for Lightweight Directory Access Protocol (LDAP), versions 2 and 3 |
Active Directory is a server for LDAP. [MS-ADTS] section 3.1.1.3 specifies the extensions and variations of LDAP that are supported by Active Directory. Note In a reference to LDAP without a version number, LDAP refers to both versions 2 and 3. |
[MS-ADTS] section 3.1.1.3.1 |
Directory Replication Service Remote Protocol (drsuapi) - Replication |
The Directory Replication Service (DRS) Remote Protocol. This protocol includes the drsuapi and dsaop RPC interfaces. Methods on these interfaces provide replication of directory information among the domain controllers of an AD DS domain. Methods on these interfaces also provide a variety of functionality to clients, such as converting names between formats and retrieving information about AD DS domain controllers. This protocol also supports DC cloning operations.<2> |
|
SMTP Replication Protocol Extensions |
The Directory Replication Service (DRS) Protocol Extensions for SMTP. This protocol provides Simple Mail Transfer Protocol (SMTP) transport of replication information as an alternative to RPC. |
|
Directory Services Setup Remote Protocol |
The Directory Services Setup Remote Protocol, as defined in [MS-DSSP]. This protocol can be used to retrieve information about the state of a computer in a domain or a non-domain workgroup. |
[MS-DSSP] |
The protocols in the following table enable account maintenance when the Active Directory system is operating in AD DS mode. This includes the creation, modification, retrieval, and deletion of users and groups.
Protocol name |
Description |
Short name |
---|---|---|
Security Account Manager (SAM) Remote Protocol (Client-to-Server) |
The Security Account Manager (SAM) Remote Protocol. Clients can use this protocol to perform account maintenance, for example, to create and delete accounts. The capabilities of this protocol are a subset of the capabilities of LDAP. |
|
Security Account Manager (SAM) Remote Protocol (Server-to-Server) |
The Security Account Manager (SAM) Remote Protocol. Domain controllers (DCs) use this protocol to forward time-critical database changes to the primary domain controller (PDC), and to forward time-critical database changes from a read-only domain controller (RODC) to a writable NC replica within the same domain outside the normal replication protocol. This protocol is used only between Active Directory servers in the same domain. |
The protocols in the following table allow clients to retrieve security policy information and translate security identifiers (SIDs) that identity security principals, such as users, to human-readable names.
Protocol name |
Description |
Short name |
---|---|---|
Local Security Authority (Domain Policy) Remote Protocol |
The Local Security Authority (Domain Policy) Remote Protocol. Clients can use this protocol to retrieve security policy information. |
|
Local Security Authority (Translation Methods) Remote Protocol |
The Local Security Authority (Translation Methods) Remote Protocol. Clients can use this protocol to translate security identifiers (SIDs) of security principals to human-readable names, and vice versa. |
The protocols in the following table enable Web services for the Active Directory system that allow access to the directory tree and the management of Active Directory account information and topologies.
Protocol name |
Description |
Short name |
---|---|---|
Active Directory Web Services Custom Action Protocol |
The Active Directory Web Services Custom Action Protocol. It is a SOAP-based Web Services protocol for managing account and topology information. |
|
WS-Transfer: Identity Management Operations for Directory Access Extensions |
WS-Transfer: Identity Management Operations for Directory Access Extensions. This is a set of protocol extensions to WS-Transfer that allows directory objects to be manipulated at a finer level of granularity than unextended WS-Transfer. |
|
WS-Enumeration: Web Services Enumeration |
The WS-Enumeration protocol. This protocol allows directory objects to be queried by using a SOAP-based Web Services protocol. |
|
WS-Transfer: Web Services Transfer |
The WS-Transfer protocol. This protocol allows directory objects to be created, removed, modified, and read by using a SOAP-based Web Services protocol. |
|
WS-Enumeration: Directory Services Protocol Extensions |
The WS-Enumeration Directory Services Protocol Extensions. This is a set of protocol extensions to WS-Enumeration that, among other things, allows a client to request that query results be sorted. It also specifies a query language that is used by clients to specify which directory objects are to be returned from the query. |
|
WS-Transfer and WS-Enumeration Protocol Extension for Lightweight Directory Access Protocol v3 Controls |
WS-Transfer and WS-Enumeration Protocol Extension for Lightweight Directory Access Protocol v3 Controls. This is a protocol extension to WS-Transfer and WS-Enumeration. It permits LDAP extended controls to be attached to operations in the protocols that it extends. |
|
Active Directory Web Services: Data Model and Common Elements |
The Active Directory Web Services: Data Model and Common Elements. Although not a protocol itself, this defines an XML data model that is shared by the other Web Service protocols and protocol extensions, as well as common protocol elements referenced by the other documents. |