000029903 - How to adjust the AFX Test Connector Capabilities Timeout value in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Oct 29, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000029903
Applies ToRSA Product Set: Identity Governance & Lifecycle 

RSA Version/Condition: All

IssueThe capabilities of Access Fulfillment Express (AFX) connectors in RSA Identity Governance & Lifecycle may be individually tested by using the Test Connector Capabilities button in the connector definition when the connector is in Test mode. (AFX > Connectors > {connector-name} > Test Connector Capabilities). Note that the Test Connector Capabilities button is disabled when the connector is in an Active state. To enable the button, edit the connector and change the state to Test.

This RSA Knowledge Base Article describes how to modify the timeout value for a specific connector capability. This can be useful for testing a capability that is not having a connection timeout issue but rather, just needs more time to complete.
ResolutionThe timeout value for a specific AFX connector capability can be modified when testing the capability.
  1. In the RSA Identity Governance & Lifecycle user interface, go to AFX > Connectors > {connector-name} > Test Connector Capabilities. 
  2. Drag one or more capabilities to the Test Suite area.
  3. Note the Timeout test in 60 Seconds. This is the default setting and where the timeout value may be modified. The value may be set to seconds or minutes from the drop-down menu. This modification is only good for the time the capability. is being tested. Once the Test Suite is closed out, the timeout value goes back to the default.


User-added image

Note that if you require large timeout settings, for example, 3-4 minutes for a single capability to complete, this is an indication of a connectivity and/or performance issue in your environment. If a capability does not complete at all regardless of how high the timeout setting, this indicates a connection issue.