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 436Number of Views Authentication Manager How to Retrieve the LDAPS Certificate and Configure an External Identity Source to Use LDAPS 4.25KNumber of Views RSA Authentication Manager Displays Unwanted Certificate Signing Requests (CSRs) in the Operations Console Certificate Man… 2.65KNumber of Views Certificate not verified error when changing Active Directory identity source from LDAP to LDAPS in RSA Authentication Man… 678Number of Views Guide to Microsoft Active Directory LDAP synchronization with RSA Authentication Manager 310Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process Download RSA SecurID Access Cloud Administration audit logs using Cloud Administration REST API CLU
Don't see what you're looking for?