Content-Type header parameter is required for Web Service in RSA Identity Governance & Lifecycle
Originally Published: 2018-04-30
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
SecurID prompt does not appear using Chrome and Firefox after adding a Security Policy on RSA Agent 8.0.3 for Apache web s… 32Number of Views Email is sending HTML content in the subject line in RSA Identity Governance & Lifecycle 29Number of Views After applying a patch, an 'ORA-06502: PL/SQL: numeric or value error: character string buffer too small' error occurs whe… 163Number of Views A PKCS#10 request through the enrollment server fails with an invalid signature error 42Number of Views Upgrade of Cisco IDS version causes collection of data to stop 30Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager Upgrade Process
Don't see what you're looking for?