Generic REST Collector ignores the Response Timeout Setting configured in the Collector Definition in RSA Identity Governance & Lifecycle
Originally Published: 2020-04-22
Last Modified: 2023-10-06
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 Test Authentication Token fails with 'Error encountered while fetching token, Status Code: 4… 251Number of Views Timeout when editing a collector in RSA Governance & Lifecycle 148Number of Views Salesforce Collector is throwing 'Invalid Credentials' error after patching to RSA Governance & Lifecycle 8.0.0 P06 8Number of Views RSA Via Lifecycle and Governance - How to set up an environment to run WebServices with Turkish Characters 14Number of Views Generic REST Collector problems with Authentication (OAuth2, Bearer Token or Basic Authentication) in RSA Governance & Lif… 367Number of Views
Trending Articles
Troubleshooting RSA MFA Agent for Microsoft Windows Deploy an Identity Router Virtual Machine in Microsoft Azure How to Change the Token Lifetime Extension Window in Authentication Manager Using rsautil How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device When configuring LDAP or LDAPS in RSA Authentication Manager with a global catalog the connection fails
Don't see what you're looking for?