000038994 - Generic REST Collector test fails with 'Unexpected response content type received. Expected content type is: application/json but received:{1}' in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 18, 2020Last modified by RSA Customer Support Employee on Jul 6, 2020
Version 5Show Document
  • View in full screen mode

Article Content

Article Number000038994
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.2.0
 
IssueWhen testing the generic REST collector (Collectors > {Collector type} > {Collector name} > Test), the following error occurs: 
 
Unexpected response content type received. Expected content type is: application/json but received:{1}
Check logs for details.

 


User-added image


The Request Headers in the collector definition are configured as follows:
User-added image



The following error is logged to the aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log):


04/30/2020 17:08:43.611 ERROR (ApplyChangesPerformQueryThread-372)
[com.aveksa.client.genericrest.postprocessor.impl.GenericRESTPostprocessorImpl]
Unexpected response content type: { Expected: application/json, Received: , Response Content: {"d":{"results":[{"__metadata": ...
...
04/30/2020 17:08:43.613 ERROR (ApplyChangesPerformQueryThread-372)
[com.aveksa.collector.generic.rest.adc.GenericRESTAccountDataReader]
Error in Test Rest API:  com.aveksa.client.genericrest.GenericRestException: UNEXPECTED_RESPONSE_CONTENT_TYPE application/json
at com.aveksa.client.genericrest.GenericRestException.connectionError(GenericRestException.java:108)

 
Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment if you are on a WildFly cluster or a non-WildFly platform. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)


 
CauseThis error occurs when the data source returns a response header in lowercase, i.e. content-type. The RSA Identity Governance & Lifecycle collector expects the response header to be in camelCase, i.e. Content-Type.
An example of a datasource that returns a lowercase response header is SAP as seen when using a software development tool such as Postman to test the API:
 
User-added image


 
ResolutionThis issue is resolved in RSA Identity Governance & Lifecycle 7.2.0 P02.
 

Attachments

    Outcomes