000034572 - Test connector settings of an Active Directory LDAP AFX connector configured to use SSL over port 636 fails with 'Failed connector settings test, Request timed out' in RSA Identity Governance & Lifecycle 

Document created by RSA Customer Support Employee on Dec 19, 2016Last modified by RSA Customer Support on Oct 31, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000034572
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.0.1
IssueWhen testing the connector settings of an Active Directory LDAP AFX connector that is configured to use SSL over port 636 (AFX > Connectors > {connector-name} > Test Connector Settings), the test fails with the following message:
     Failed connector settings test. Request timed out.     

     User-added image   


     The Active Directory LDAP AFX connector log,       $AFX_HOME/esb/logs/esb.AFX-CONN-{connector-name}.log shows the following error.     

2016-12-12 11:19:52.205 [ERROR] org.mule.module.launcher.application.DefaultMuleApplication:361
- null java.lang.ClassNotFoundException: com.aveksa.common.tls.SSLContextFactory


     The AFX mule log file,       $AFX_HOME/esb/logs/mule_ee.log has a corresponding error:    

ERROR 2016-12-12 11:19:52,478 [Mule.app.deployer.monitor.1.thread.1]
+ Failed to deploy artifact 'AFX-CONN-AD-AFX-Connector',   +
+ see below                                                +
org.mule.module.launcher.DeploymentStartException: ClassNotFoundException:

The same connector configured to connect over port 389 (non-SSL connection) is able to connect.

CauseThis is a known issue in RSA Identity Governance & Lifecycle 7.0.1 GA (release) version.

The key errors are the java.lang.ClassNotFoundException: and ClassNotFoundException: errors in the AFX log files. This error occurs due to a missing class file in the mmc-console class path.

ResolutionThis issue is resolved in RSA Identity Governance and Lifecycle 7.0.1 P01.