Generic REST Collector ignores the Response Timeout Setting configured in the Collector Definition in RSA Identity Governance & Lifecycle
Originally Published: 2020-04-22
Article Number
Applies To
RSA Version/Condition: 7.2.0
Issue
In the example below, the Response Timeout is set to 10000 milliseconds (10 seconds). A test of the collector that fails to connect to the endpoint is expected to timeout after 10 seconds. Instead it takes four to five minutes to timeout.
Go to Collectors > Collector Type > {Collector Name} > Test button
Collector test failed:
com.aveksa.server.runtime.ServerException: Test request failed with response: Request timed out
com.aveksa.server.runtime.ServerException: Test request failed with response: Request timed out
Cause
Resolution
Related Articles
Generic REST Collector fails with 'jsonpath.PathNotFoundException:Missing property in path $['members']' error collecting … 80Number of Views Generic REST Collector "Unexpected response content type" in RSA Governance & Lifecycle 62Number of Views Federated Salesforce Account Collector fails with 'Invalid Credentials' in RSA Identity Governance & Lifecycle 118Number of Views Generic REST Collector ignores Proxy setting in RSA Identity Governance & Lifecycle 73Number of Views Generic REST Collector Test Authentication Token fails with 'Error encountered while fetching token, Status Code: 4… 237Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?