AnsweredAssumed Answered

AFX connector time out

Question asked by vasudev verma on May 4, 2016
Latest reply on Jan 5, 2017 by Sunita Bhat

Like • Show 0 Likes0
Comment • 9

Hi All,

We are trying to create connectors for AD and OpenLDAP, over SSL. After filling up the connection details, when we test the connector settings, an error message is displayed, " Connector test failed: response time out ". We have changed the time out settings at both end but still the issue persists. What is more surprising, if we create Directory, which eventually creates the connector and account collector, when testing the connection with the collector, it's working perfectly fine. Issue is when trying to connect using the connector. Checked for the connectivity to the SSL port, found no issue.

Any idea what could be the issue. Sharing the error screenshot below

Thanks,

Vasu

No one else has this question

Outcomes

9 Replies

Ted Barbour May 4, 2016 8:17 AM
Mark Correct
Correct Answer
Hi Vasu - are you saying that if you create a Directory using the wizard that the wizard-created collector works but the wizard-created connector does not? Or are you saying the wizard works but manually creating a connector is failing? Screen shots of working settings vs not working would be helpful. RSA Via L&G version/patch info would also be helpful.
Like • Show 0 Likes0
Actions
- vasudev verma @ Ted Barbour on May 4, 2016 9:13 AM
  Mark Correct
  Correct Answer
  Hi Ted,
  
  Yes, when we try to create a connector using create connector wizard, it failing to connect to the LDAP, but when creating a directory using the create directory wizard, it's able to connect to the LDAP. Sharing the screen shot. We are working on RSA Visa L&G Version 7.0 .
  Like • Show 0 Likes0
  Actions
  - Ted Barbour @ vasudev verma on May 4, 2016 9:54 AM
    Mark Correct
    Correct Answer
    Sorry I'm still not understanding your scenario. The 2 screen shots are for a connector and a collector.
    Does the Directory wizard produce a connector that works? If so can you show the connection settings for working connector?
    Like • Show 0 Likes0
    Actions
    - vasudev verma @ Ted Barbour on May 5, 2016 2:24 AM
      Mark Correct
      Correct Answer
      We have created a directory for OpenLDAP , which created a collector and a connector. Issue is, the connector is not able to connect to the ldap while the collector is able to.
      
      We tried creating a new connector for OpenLDAP using the "Create Connector" wizard, but facing the face problem.
      Like • Show 0 Likes0
      Actions
      - Boris Lekumovich @ vasudev verma on May 5, 2016 3:35 AM
        Mark Correct
        Correct Answer
        What happens when you try to change the connection settings to non secure (see screenshot below)?
        
        When creating a connector manually, what type of Connector template did you choose (Active Directory or OpenLDAP)?
        
        Like • Show 0 Likes0
        Actions
        vasudev verma @ Boris Lekumovich on May 5, 2016 5:26 AM
        Mark Correct
        Correct Answer
        We did tried connecting over non-ssl port (in our case port 1389) but got the same error. We are using the OpenLDAP template for creating the connector.
        Like • Show 0 Likes0
        Actions
        Boris Lekumovich @ vasudev verma on May 5, 2016 8:03 AM
        Mark Correct
        Correct Answer
        See what's going on in the logs (aveksaServer.log and the AFX logs)
        Like • Show 0 Likes0
        Actions
        vasudev verma @ Boris Lekumovich on May 11, 2016 8:52 AM
        Mark Correct
        Correct Answer
        snippet from the AFC.main.log
        
        2016-05-11 17:09:30.965 [INFO] org.mule.module.client.MuleClient:193 - Using existing MuleContext: org.mule.DefaultMuleContext@68bb4261
        2016-05-11 17:09:30.978 [INFO] org.apache.commons.httpclient.auth.AuthChallengeProcessor:193 - basic authentication scheme selected
        2016-05-11 17:09:30.981 [INFO] org.apache.commons.httpclient.HttpMethodDirector:193 - Failure authenticating with BASIC 'Galaxy Realm'@localhost:8585
        2016-05-11 17:09:30.984 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:77 - Unable get/setup the server id from the MMC request
        2016-05-11 17:09:30.985 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:78 - Retrying MMC connection and server id setup...
        2016-05-11 17:09:35.986 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:81 - Connection request retry attempt #1 of 12
        2016-05-11 17:09:36.114 [INFO] org.apache.commons.httpclient.auth.AuthChallengeProcessor:193 - basic authentication scheme selected
        2016-05-11 17:09:36.115 [INFO] org.apache.commons.httpclient.HttpMethodDirector:193 - Failure authenticating with BASIC 'Galaxy Realm'@localhost:8585
        2016-05-11 17:09:36.117 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:77 - Unable get/setup the server id from the MMC request
        2016-05-11 17:09:36.118 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:78 - Retrying MMC connection and server id setup...
        2016-05-11 17:09:41.118 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:81 - Connection request retry attempt #2 of 12
        2016-05-11 17:09:41.147 [INFO] org.apache.commons.httpclient.auth.AuthChallengeProcessor:193 - basic authentication scheme selected
        2016-05-11 17:09:41.148 [INFO] org.apache.commons.httpclient.HttpMethodDirector:193 - Failure authenticating with BASIC 'Galaxy Realm'@localhost:8585
        2016-05-11 17:09:41.153 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:77 - Unable get/setup the server id from the MMC request
        2016-05-11 17:09:41.155 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:78 - Retrying MMC connection and server id setup...
        2016-05-11 17:09:46.156 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:81 - Connection request retry attempt #3 of 12
        2016-05-11 17:09:46.175 [INFO] org.apache.commons.httpclient.auth.AuthChallengeProcessor:193 - basic authentication scheme selected
        2016-05-11 17:09:46.178 [INFO] org.apache.commons.httpclient.HttpMethodDirector:193 - Failure authenticating with BASIC 'Galaxy Realm'@localhost:8585
        2016-05-11 17:09:46.180 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:77 - Unable get/setup the server id from the MMC request
        2016-05-11 17:09:46.202 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:78 - Retrying MMC connection and server id setup...
        2016-05-11 17:09:51.203 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:81 - Connection request retry attempt #4 of 12
        2016-05-11 17:09:51.215 [INFO] org.apache.commons.httpclient.auth.AuthChallengeProcessor:193 - basic authentication scheme selected
        2016-05-11 17:09:51.216 [INFO] org.apache.commons.httpclient.HttpMethodDirector:193 - Failure authenticating with BASIC 'Galaxy Realm'@localhost:8585
        2016-05-11 17:09:51.276 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:77 - Unable get/setup the server id from the MMC request
        2016-05-11 17:09:51.276 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:78 - Retrying MMC connection and server id setup...
        2016-05-11 17:09:56.277 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:81 - Connection request retry attempt #5 of 12
        2016-05-11 17:09:56.283 [INFO] org.apache.commons.httpclient.auth.AuthChallengeProcessor:193 - basic authentication scheme selected
        2016-05-11 17:09:56.284 [INFO] org.apache.commons.httpclient.HttpMethodDirector:193 - Failure authenticating with BASIC 'Galaxy Realm'@localhost:8585
        2016-05-11 17:09:56.286 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:77 - Unable get/setup the server id from the MMC request
        2016-05-11 17:09:56.286 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:78 - Retrying MMC connection and server id setup...
        2016-05-11 17:10:01.287 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:81 - Connection request retry attempt #6 of 12
        2016-05-11 17:10:01.296 [INFO] org.apache.commons.httpclient.auth.AuthChallengeProcessor:193 - basic authentication scheme selected
        2016-05-11 17:10:01.297 [INFO] org.apache.commons.httpclient.HttpMethodDirector:193 - Failure authenticating with BASIC 'Galaxy Realm'@localhost:8585
        2016-05-11 17:10:01.299 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:77 - Unable get/setup the server id from the MMC request
        2016-05-11 17:10:01.299 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:78 - Retrying MMC connection and server id setup...
        2016-05-11 17:10:06.300 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:81 - Connection request retry attempt #7 of 12
        2016-05-11 17:10:06.309 [INFO] org.apache.commons.httpclient.auth.AuthChallengeProcessor:193 - basic authentication scheme selected
        2016-05-11 17:10:06.310 [INFO] org.apache.commons.httpclient.HttpMethodDirector:193 - Failure authenticating with BASIC 'Galaxy Realm'@localhost:8585
        2016-05-11 17:10:06.313 [WARN] com.aveksa.afx.server.manager.MMCRequestManagerImpl:77 - Unable get/setup the server id from the MMC request
        2016-05-11 17:10:31.503 [ERROR] com.aveksa.afx.server.manager.MMCRequestManagerImpl:208 - Error stopping application AFX-CONN-External-Users-Connector
        com.aveksa.afx.server.manager.MMCException: Failed to get flows for server. No associated server Id. Check Request Manager Initialization
        Like • Show 0 Likes0
        Actions
        Sunita Bhat @ vasudev verma on Jan 5, 2017 11:58 AM
        Mark Correct
        Correct Answer
        We have having similar errors in the log:
        
        Unable to get status for all Connectors from MMC
        com.aveksa.afx.server.manager.MMCException: Failed to get flows for server. No associated server Id. Check Request Manager Initialization
        
        Any idea what was causing this in your instance?
        Like • Show 0 Likes0
        Actions