Back learn.microsoft.com Enable Ldap Signing In Windows Server
Access to this page requires authorization. You can try signing in or changing directories .
Access to this page requires authorization. You can try changing directories .
Applies to: Supported versions of Windows Server
This article describes how to enable LDAP signing in Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows 10, and Windows 11.
Original KB number: 935834
You can significantly improve the security of a directory server by configuring the server to reject Simple Authentication and Security Layer (SASL) LDAP binds that do not request signing (integrity verification), or to reject LDAP simple binds that are performed on a clear text (non-SSL/TLS-encrypted) connection. SASL binds may include protocols such as Negotiate, Kerberos, NTLM, and Digest.
Unsigned network traffic is susceptible to replay attacks. In such attacks, an intruder intercepts the authentication attempt and the issuance of a ticket. The intruder can reuse the ticket to impersonate the legitimate user. Additionally, unsigned network traffic is susceptible to man-in-the-middle (MIM) attacks in which an intruder captures packets between the client and the server, changes the packets, and then forwards them to the server. If this occurs on an LDAP server, an attacker can cause a server to make decisions that are based on forged requests from the LDAP client.
How to discover clients that do not use the Require signing option
After you make this configuration change, clients that rely on unsigned SASL (Negotiate, Kerberos, NTLM, or Digest) LDAP binds or on LDAP simple binds over a non-SSL/TLS connection stop working. To help identify these clients, the directory server of Active Directory Domain Services (AD DS) or Lightweight Directory Server (LDS) logs a summary Event ID 2887 one time every 24 hours to indicate how many such binds occurred. We recommend that you configure these clients not to use such binds. After no such events are observed for an extended period, we recommend that you configure the server to reject such binds.
If you must have more information to identify such clients, you can configure the directory server to provide more detailed logs. This additional logging will log an Event ID 2889 when a client tries to make an unsigned LDAP bind. The log entry displays the IP address of the client and the identity that the client tried to use to authenticate. You can enable this additional logging by setting the 16 LDAP Interface Events diagnostic setting to 2 (Basic) . For more information how to change the diagnostic settings, see How to configure Active Directory and LDS diagnostic event logging .
If the directory server is configured to reject unsigned SASL LDAP binds or LDAP simple binds over a non-SSL/TLS connection, the directory server logs a summary Event ID 2888 one time every 24 hours when such bind attempts occur.
For information possible affects of changing security settings, see Client, service, and program issues can occur if you change security settings and user rights assignments .
How to set the server LDAP signing requirement
Select Start > Run , type mmc.exe , and then select OK .
Select File > Add/Remove Snap-in , select Group Policy Management Editor , and then select Add .
Select Group Policy Object > Browse .
In the Browse for a Group Policy Object dialog box, select Default Domain Controller Policy under the Domains, OUs, and linked Group Policy Objects area, and then select OK .
Select Default Domain Controller Policy > Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies , and then select Security Options .
Right-click Domain controller: LDAP server signing requirements , and then select Properties .
In the Domain controller: LDAP server signing requirements Properties dialog box, enable Define this policy setting , select Require signing in the Define this policy setting list, and then select OK .
In the Confirm Setting Change dialog box, select Yes .
How to set the client LDAP signing requirement by using local computer policy
Select Start > Run , type mmc.exe , and then select OK .
Select File > Add/Remove Snap-in .
In the Add or Remove Snap-ins dialog box, select Group Policy Object Editor , and then select Add .
Select Local Computer Policy > Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies , and then select Security Options .
Right-click Network security: LDAP client signing requirements , and then select Properties .
In the Network security: LDAP client signing requirements Properties dialog box, select Require signing in the list, and then select OK .
In the Confirm Setting Change dialog box, select Yes .
How to set the client LDAP signing requirement by using a domain Group Policy Object
Select Start > Run , type mmc.exe , and then select OK .
Select File > Add/Remove Snap-in .
In the Add or Remove Snap-ins dialog box, select Group Policy Object Editor , and then select Add .
Select Browse , and then select Default Domain Policy (or the Group Policy Object for which you want to enable client LDAP signing).
Select Default Domain Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies , and then select Security Options .
In the Network security: LDAP client signing requirements Properties dialog box, select Require signing in the list, and then select OK .
In the Confirm Setting Change dialog box, select Yes .
How to set the client LDAP signing requirement by using registry keys
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ \Parameters
The placeholder represents the name of the AD LDS instance that you want to change.
The registry entry has the following possible values:
0 : Signing is disabled.
2 : Signing is enabled.
When you change this value, the new value takes effect immediately. You don't have to restart the computer.
How to verify configuration changes
Sign in to a computer that has the AD DS Admin Tools installed.
Sign in to a computer that has the AD DS Admin Tools installed.
Select Start > Run , type ldp.exe , and then select OK .
Select Start > Run , type ldp.exe , and then select OK .
Select Connection > Connect .
Select Connection > Connect .
In Server and in Port , type the server name and the non-SSL/TLS port of your directory server, and then select OK . Note For an Active Directory Domain Controller, the applicable port is 389.
In Server and in Port , type the server name and the non-SSL/TLS port of your directory server, and then select OK .
For an Active Directory Domain Controller, the applicable port is 389.
After a connection is established, select Connection > Bind .
After a connection is established, select Connection > Bind .
Under Bind type , select Simple bind .
Under Bind type , select Simple bind .
Type the user name and password, and then select OK . If you receive the following error message, you have successfully configured your directory server: Ldap_simple_bind_s() failed: Strong Authentication Required
Type the user name and password, and then select OK .
If you receive the following error message, you have successfully configured your directory server:
Ldap_simple_bind_s() failed: Strong Authentication Required
Ldap_simple_bind_s() failed: Strong Authentication Required
Event reference for LDAP signing requirements
After starting DS services, Event ID 2886 is logged to remind administrators to enable signing requirements:
When a problem client is detected but permitted, a summary event (Event ID 2887) of the past 24 hours is logged:
When a problem client is rejected, a summary event (Event ID 2888) of the past 24 hours is logged:
When a problem client tries to connect, Event ID 2889 is logged:
ADV190023: Microsoft Guidance for Enabling LDAP Channel Binding and LDAP Signing
2020 LDAP channel binding and LDAP signing requirement for Windows
2020, 2023, and 2024 LDAP channel binding and LDAP signing requirements for Windows (KB4520412)
How to configure Active Directory and LDS diagnostic event logging
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?
Last updated on 2026-02-12
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
