AD connector failed to connect when SSL is turned on

Document ID : KB000093538
Last Modified Date : 11/09/2018
Show Technical Document Details
Issue:
Able to connect to our AD endpoint using AD connector in non-SSL mode.

When SSL is mode is enabled, and restarted the connector servers, we get the following error message on any operation we perform:
ETA_E_0019, Active Directory Endpoint 'ADTest' read failed: Connector Server Add failed: code 52 (UNAVAILABLE): failed to add entry eTADSDirectoryName=ADTest,eTNamespaceName=ActiveDirectory,dc=im,dc=etasa: JCS@hostname:  JNDI: Failed to activate connector on proxy connector server: [LDAP: error code 52 - Server Down] (ldaps://192.94.22.101:20411) - Return Code: 13
 
Resolution:
The error message is typically due to a certificate issue.   Please verify the certificate details.  We have seen this issue with missing certificates, as well as with configuration issues related to the certificate.  For example, using an IP address that does not match the fully qualified domain name the certificate was assigned to.
 

Please, refer to the CA Identity Management & Governance Connectors Guides for the Microsoft Active Directory, Microsoft Exchange, and Microsoft Lync connectors, :How to Connect to Active Directory for very detailed instructions on implementing the connector both in a secure, and non-secure environments:

https://docops.ca.com//display/IMGC10/How+to+Connect+to+Active+Directory