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
Authentication Token is showing in plain text in the Metadata Export for Generic REST collector in RSA Governance & Lifecycle 24Number of Views Review generation fails in RSA Via Lifecycle and Governance when double byte characters are in any of the display names de… 89Number of Views Generic REST Collector fails with GENERIC_REST_EXCEPTION_NULL_API_URL error when calling the Group Data operation in RSA I… 137Number of Views How to include descriptions in review results for RSA Identity Governance and Lifecycle 14Number of Views How to Enable AFX Connector Debug Logging in RSA Identity Governance & Lifecycle 8.79KNumber of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?