Workflow Web Service node fails with Illegal character(s) in message header value in RSA Identity Governance & Lifecycle
Originally Published: 2018-03-09
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 7.0.2+
Issue
SOAP request is failed error.
The complete error message in the aveksaServer.log is:
03/04/2018 00:13:13.890 ERROR (Worker_actionq#Script Queue - Normal#WPDS_8)
[com.aveksa.server.workflow.webservices.soap.client.SoapClient]
SoapClient: handleSoapRequest: Exception: java.lang.IllegalArgumentException:
Illegal character(s) in message header value:
Basic dWlkPVNWQ19VQU1fQ0FHTSxvdT1pZGVudGl0eW1pLGRjPWlzdG9vb2xvbmcsZGM9Q09NOmRkZGRk
In this example, the SOAP web service node is defined in an approval workflow.
When the 1 error hyperlink is clicked the error shown is:
SOAP request is failed.
Cause
Resolution
Related Articles
1 Virtual Disk(s) Degraded error or 1 Virtual Disk(s) is in Critical State error displays when RSA SecurID A250 Hardware A… 41Number of Views RSA SDK 4.1 for iOS Developer's Guide and Release Notes 19Number of Views Data purging fails with "ORA-20001: No jobs were found to delete" in RSA Identity Governance & Lifecycle 7.1.1 63Number of Views When a role is removed from a user based on a revocation date, the entitlement(s) belonging to that role are not removed f… 38Number of Views Unable to start RSA ACE/Server services after stopping them when Quick Admin was used prior to stop 29Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?