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
The URL parameter SSOLogin=false fails to bypass SSO login after upgrading to 7.0.2 of RSA Identity Governance & Lifecycle 132Number of Views Termination rule not generating a change request to disable the manually mapped accounts in RSA Identity Governance & Life… 43Number of Views New feature for RSA Identity Governance & Lifecycle 7.1: Workflow System Status 321Number of Views There is no option to clear the mysql-connector-java-{version}-bin.jar file from the MySQL AFX connector template in RSA I… 200Number of Views AFX Server installs on Windows in a non-functional state due to JAVA_HOME in RSA Governance & Lifecycle 29Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide User Application Portal The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn… RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" How to Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console
Don't see what you're looking for?