|Applies To||RSA Product Set: Identity Management and Governance|
RSA Version/Condition: 6.9.1
Platform (Other): Linux
|Issue||When configuring an Access Fulfillment Express (AFX) Connector for RESTful Web Services, the Add Application Role to Account capability has the following default Request Header settings:|
However, when AFX is processing the response from the RESTful Web Service, a message with the following properties and error message may be returned.
The below error may be logged during parsing of the http web service response:
|Cause||The RESTful Web Wervice is providing a Content Type of: application/xml; charset=UTF-8, but the expected value is just: application/xml.|
To enable AFX DEBUG, please review the following articles:
2016-10-12 09:23:45.675 [DEBUG] org.mule.module.scripting.transformer.ScriptTransformer:125 - Object after transform: Error processing RESTful web service response: java.lang.IllegalStateException: Expected application/xml but received application/xml; charset=UTF-8
|Resolution||So that it meets the JMS specification (sec. 3.5.1, 126.96.36.199), the RESTful Web Service needs to send:|
This is in accordance with the message:
org.mule.transport.jms.JmsMessageUtils:269 - Header: Content-Type is not compliant with JMS specification (sec. 3.5.1, 188.8.131.52).
|Workaround||It may not be possible to correct the Content-Type being sent by the RESTful Web Service. In this situation, RSA Identity Governance and Lifecycle allows the expected Content-Type to be adjusted.|
To resolve the problem, update the Request Header Content-Type in the Connector Capabilities, so that is matches what is being sent by the RESTful Web Service; for example,
set Content-Type to: application/xml; charset=UTF-8