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
Form control type 'Drop Down Select with Web Service' displays Unauthorized error in RSA Identity Governance & Lifecycle 7… 145Number of Views Overview of using the Linux curl command to interact with the Web Services API in RSA Identity Governance & Lifecycle 701Number of Views How to Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console 3.29KNumber of Views Unauthorized message for Drop Down Select with Web Service in RSA Identity Governance & Lifecycle 53Number of Views Unable to load form fields when using a form element of control type "Drop Down with Web Service" in RSA Identity Governan… 95Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Detect and Resolve Stalled Workflows and Workpoint Issues in RSA Identity Governance & Lifecycle How to change the default Oracle Statistics History Retention period for RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Installation Guide RSA Authentication Manager Patch Updates
Don't see what you're looking for?