This is a known issue in the following version:
- SecurID Governance & Lifecycle 7.5.2 P06
The Generic REST Collector may fail in the following manner.
When using OAuth2, the initial authentication (initial collection) may succeed but the OAuth token fails when refreshed. The following may be logged in the aveksaServer.log file:
06/09/2023 12:44:32.175 ERROR (pool-32-thread-1) [com.aveksa.server.core.oauth2.OAuth2Handler] Error occured while generating access token from refresh token
com.aveksa.server.core.oauth2.OAuth2Exception: Error occured while generating access token from refresh token : Unauthorized
When using Basic authentication (username and password) the collection will fail. The following may be logged in the aveksaServer.log file:
06/29/2023 13:49:09.565 ERROR (Thread-70 (ActiveMQ-client-global-threads)) [com.aveksa.server.utils.NodeMessageBroker] Exception while getting test data from collector
com.aveksa.server.runtime.ServerException: com.aveksa.common.DataReadException: com.aveksa.client.genericrest.GenericRestException: UNEXPECTED_RESPONSE_CONTENT_TYPE application/json [text/html; charset=utf-8].
When using a Bearer Token, the collection may fail.
The test of the Generic Rest Collector shows "401 Unauthorized".
The system is incorrectly base64 encoding the values stored in the database for the OAuth2 token, password and/or bearer token.
This issue is resolved in the following versions:
- SecurID Governance & Lifecycle 7.5.2 P08
- RSA Governance & Lifecycle 8.0.0
