Test connection failed. One or more directory connections is incorrect error during testing connection from RSA Authentication Manager and Active Directory
Originally Published: 2016-08-29
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Issue
When testing, the following error displays:
There was a problem processing your request.
Test connection failed. One or more directory connections is incorrect.
Testing from an SSH session with open_ssl s_client is successful:
rsaadmin@am1p:~> openssl s_client -connect 192.168.2.120:389 CONNECTED(00000003) write:errno=104 rsaadmin@am1p:~> openssl s_client -connect 192.168.2.120:636 CONNECTED(00000003)
In a packet capture from RSA Authentication Manager, you find that the connection failed with the following error, as shown in the screenshot below:
The server requires binds to turn on integrity checking if SSL/TLS are not already active on the connection.
Cause
How to check the server LDAP signing requirement:
- Click Start > Run.
- In the text box, type mmc.exe, and then click OK.
- On the File menu, click Add/Remove Snap-in.
- In the Add or Remove Snap-ins dialog box, click Group Policy Management Editor, and then click Add.
- In the Select Group Policy Object dialog box, click Browse.
- In the Browse for a Group Policy Object dialog box, click Default Domain Policy under the Domains, OUs and Linked Group Policy Objects area.
- Click OK.
- Click Finish.
- Click OK.
- Expand the Default Domain Controller Policy.
- Expand Computer Configuration.
- Expand Policies.
- Expand Windows Settings.
- Expand Security Settings.
- Expand Local Policies.
- Click Security Options.
- Right click on the domain controller:
- Select LDAP server signing requirements and click Properties.
- In the domain controller, in the LDAP server signing requirements properties dialog box, enable Define this policy setting.
- Click to select Require signing in the Define this policy setting drop-down list, and then click OK.
- In the Confirm Setting Change dialog box, you find the value is Require Signing.
Resolution
- Change the policy on the AD from Require Signing to None. This allows the RSA Authentication Manager to connect to the Active Directory through LDAP protocol.
- Change the protocol that is used on the Operations Console from LDAP to LDAPS. This requires you to import the AD certificate to RSA Authentication Manager. Follow the steps to get the external Identity Source LDAPS certificate using openssl for Authentication Manager 8.1.
Related Articles
Test connection fails from the RSA ID Plus Cloud Access Service and Identity Router to the SecurID Authentication Manager 1.35KNumber of Views Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures 2.5KNumber of Views AFX test connector settings button times out and the test connector capabilities work or the test connector capabilities f… 383Number of Views How to test RSA Identity Router (IDR) Secure Connector connectivity to the RSA ID Plus Cloud Access Service 2.44KNumber of Views How to test RSA SecurID Authentication Manager to ID Plus Cloud Access Service connectivity 819Number of Views
Trending Articles
An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process
Don't see what you're looking for?