How to enable DEBUG level logging for the Generic REST Connector in RSA Governance & Lifecycle
2 years ago
Article Number
000072186
Applies To
  • SecurID Governance & Lifecycle 7.5.2 P08
  • RSA Governance & Lifecycle 8.0.0 P01
Resolution
The following versions introduce additional DEBUG level logging classes for the Generic REST Connector. 
  • SecurID Governance & Lifecycle 7.5.2 P08
  • RSA Governance & Lifecycle 8.0.0 P01

From the Logs menu on the Admin/Diagnostics tab click the Settings button and then Use the Advanced button to add the following com.aveksa classed at the DEBUG log level.

com.aveksa.client.genericrest.preprocessor.impl.GenericRESTPreProcessorImpl
and
com.aveksa.client.genericrest.postprocessor.impl.GenericRESTPostprocessorImpl

 

image1.png

This adds additional logging to the aveksaserver.log file that contain both the REQUEST and the RESPONSE objects. 

For example:

com.aveksa.client.genericrest.preprocessor.impl.GenericRESTPreProcessorImpl

05/08/2024 10:52:59.857 DEBUG (ApplyChangesPerformQuery-1713976410136-1713976410136) [com.aveksa.client.genericrest.preprocessor.impl.GenericRESTPreProcessorImpl] Starting Generic REST prepareRequest() method
05/08/2024 10:52:59.859 DEBUG (ApplyChangesPerformQuery-1713976410136-1713976410136) [com.aveksa.client.genericrest.preprocessor.impl.GenericRESTPreProcessorImpl] Request header: {Accept=application/json, Authorization=Bearer ${AuthenticationToken}}
05/08/2024 10:52:59.860 DEBUG (ApplyChangesPerformQuery-1713976410136-1713976410136) [com.aveksa.client.genericrest.preprocessor.impl.GenericRESTPreProcessorImpl] Request type: GET
05/08/2024 10:52:59.860 DEBUG (ApplyChangesPerformQuery-1713976410136-1713976410136) [com.aveksa.client.genericrest.preprocessor.impl.GenericRESTPreProcessorImpl] Request body: null
05/08/2024 10:52:59.860 DEBUG (ApplyChangesPerformQuery-1713976410136-1713976410136) [com.aveksa.client.genericrest.preprocessor.impl.GenericRESTPreProcessorImpl] Starting Generic REST prepareConnection() method
05/08/2024 10:52:59.861 DEBUG (ApplyChangesPerformQuery-1713976410136-1713976410136) [com.aveksa.client.genericrest.preprocessor.impl.GenericRESTPreProcessorImpl] Base URL: https://acm-800p01.vcloud.local:8443
05/08/2024 10:52:59.861 DEBUG (ApplyChangesPerformQuery-1713976410136-1713976410136) [com.aveksa.client.genericrest.preprocessor.impl.GenericRESTPreProcessorImpl] URL: https://acm-800p01.vcloud.local:8443/aveksa/command.submit?cmd=findAccounts&returnMaxRows=20&format=json

 

And 

com.aveksa.client.genericrest.postprocessor.impl.GenericRESTPostprocessorImpl

 

04/24/2024 18:21:07.515 DEBUG (ApplyChangesChangeDataRequest-1713976410127-1713976410127) [com.aveksa.client.genericrest.postprocessor.impl.GenericRESTPostprocessorImpl] Inside getParsedData() method of GenericRESTPostProcessor
04/24/2024 18:21:07.516 DEBUG (ApplyChangesChangeDataRequest-1713976410127-1713976410127) [com.aveksa.client.genericrest.postprocessor.impl.GenericRESTPostprocessorImpl] Response header: {content-type=[application/json], set-cookie=[JSESSIONID="YvIoel8j0g3w_m3OTF2JCpOkTZTpPhx5IUEHI9wv.master:img-server-1"; Version=1; Path=/aveksa; HttpOnly], connection=[keep-alive], date=[Wed, 24 Apr 2024 22:21:07 GMT], x-content-type-options=[nosniff], transfer-encoding=[chunked], content-security-policy=[default-src 'self';script-src 'self' 'unsafe-inline' 'unsafe-eval';style-src 'self' 'unsafe-inline';font-src 'self' https://fonts.gstatic.com;img-src 'self' data:;frame-src * blob: data:;], content-disposition=[inline;filename=findAccounts_1713997267505.json]}
04/24/2024 18:21:07.516 DEBUG (ApplyChangesChangeDataRequest-1713976410127-1713976410127) [com.aveksa.client.genericrest.postprocessor.impl.GenericRESTPostprocessorImpl] Response status code: 200
04/24/2024 18:21:07.516 DEBUG (ApplyChangesChangeDataRequest-1713976410127-1713976410127) [com.aveksa.client.genericrest.postprocessor.impl.GenericRESTPostprocessorImpl] Response body: {
"findAccounts":[
{"id":"1","name":"Younge","creation_date":"2023-12-14 15:25:02.0","deletion_date":"","application_id":"2","adc_id":"4","adc_name":"Active Directory ADC","is_shared":"n","last_login_date":"","orphaned_date":"","is_locked":"0","is_disabled":"0","object_sid":"","expiration_date":"","account_expires":"","acc_date":"","acc_number":"","user_account_control":"NORMAL_ACCOUNT,DONT_EXPIRE_PASSWORD","external_id":"CN=van Sinderen\\, Eline,OU=SE,OU=vcloud Users,DC=2k8r2-vcloud,DC=local","account_type":"","acc_string":"","last_reviewed_date":"","cad4":"","cad5":"","cai5":"","cas8":"NORMAL_ACCOUNT,DONT_EXPIRE_PASSWORD","cas9":"CN=van Sinderen\\, Eline,OU=SE,OU=vcloud Users,DC=2k8r2-vcloud,DC=local","cas19":"","cas20":""},

 

 


WARNING:  RSA recommends DEBUG logging be enabled only in DEV or TEST instances.  Use DEBUG level logging cautiously in PROD environments. 

WARNING: Disable DEBUG level logging and DEBUG level logging classes immediately after use.  DEBUG level logging can adversely affect performance.   Prolonged use of DEBUG level logging can cause the system to run out of database and or filesystem resources and lead to catastrophic failure. 

Notes
There are other additional DEBUG level logging classes under com.aveksa.client.genericrest.* that may provide more information on specific issues. 

Related Articles

Trending Articles

Don't see what you're looking for?