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
There is no option to clear the mysql-connector-java-{version}-bin.jar file from the MySQL AFX connector template in RSA I… 197Number of Views 'javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path' error when testing a RESTful W… 360Number of Views Entitlement from a deleted account is still seen in the User Access tab in RSA Identity Governance & Lifecycle 114Number of Views Security Scanners Are Still Detecting CVE-2022-23302 Vulnerability in the AM Server Even After Upgrading to v8.6 Patch 3 80Number of Views RSA SecurID Software Token 5.0 for Windows Quick Start 55Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle How to Download and Reinstall the AFX Server Archive in RSA Governance & Lifecycle
Don't see what you're looking for?