When configuring LDAP or LDAPS in RSA Authentication Manager with a global catalog the connection fails
Originally Published: 2014-06-09
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x, 7.1, 3.0
Issue
There was a problem processing your request.
Test connection failed. One or more directory connections is incorrect.
Test connection failed. One or more directory connections is incorrect.
Cause
Resolution
Please see the article on how to obtain and install the Windows rootCA certificate from a domain controller to use for LDAPS and secure identity source over port 636.
LDAP
Use ports 389 for a domain controller (e. g., ldap://<fqdn> or ldap://<fqdn>:389) or 3268 for a global catalog (e. g., ldap://<fqdn>:3268).
LDAPS
Use ports 636 and 3269 for the global catalog (e. g., ldaps://<fqdn> or ldaps://<fqdn>:636) or ldap://<fqdn>:3269 for a global catalog.
Related Articles
RSA Authentication Manager and Self-Signed Certificates 424Number of Views RSA Authentication Manager Displays Unwanted Certificate Signing Requests (CSRs) in the Operations Console Certificate Man… 2.63KNumber of Views Unable to login to RSA Authentication Manager Security Console as super admin 5.24KNumber of Views Guide to Microsoft Active Directory LDAP synchronization with RSA Authentication Manager 307Number of Views RSA Authentication Manager 8.8 upgrade fails with ERROR: auth_manager.rest_service.old_access_key is not found 2.23KNumber of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?