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 Entitlement Views show zero items in RSA Identity Governance & Lifecycle after installing a 7.1.x patch 48Number of Views Partial reject for approvals still provision indirect entitlements for accounts in RSA Governance & Lifecycle 40Number of Views Termination rule not generating a change request to disable the manually mapped accounts in RSA Identity Governance & Life… 43Number of Views How to associate a field in a form in a WorkFlow email template. 55Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme AFX Server and Remote Collection Agents fail to start after updating Java to version 1.8u241 (1.8.0_241) / 1.7u251 (1.7.0_… Upgrade Internal Authentication Manager Certificates to SHA-256 RSA Authentication Manager 8.9 Setup and Configuration Guide Upgrading the Internal SecurID Authentication Manager 8.6 Certificates to SHA-256
Don't see what you're looking for?