Content-Type header parameter is required for Web Service in RSA Identity Governance & Lifecycle
Originally Published: 2018-04-30
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.0.2, 7.1.0
Issue
Content-Type header parameter is required for REST Web Service.
The same behavior exists for a SOAP Web Services node:
Content-Type header parameter is required for SOAP Web Service.
Resolution
The workflow engine requires the parameter Content-Type to be populated in the header section of the sidebar. The workflow engine does not read the header value from the request envelope/body.
Example REST Web Services node
Example SOAP Web Services node
Notes
Related Articles
'javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path' error when testing a RESTful W… 359Number of Views Remote AFX Server does not start, there is a SocketException in esb.AFX_INIT.log, and OpenSSL cannot complete an SSL Hands… 339Number of Views Methods to monitor the RSA ID Plus Cloud Authentication Service and Identity Routers 473Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?