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
000040834
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.2+

 
Issue
A  request that has a SOAP web service node in its workflow fails with the following error:

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. 
 
User-added image

When the 1 error hyperlink is clicked the error shown is:
 
SOAP request is failed.
 
User-added image
Cause
The error occurs if the usernames used in the proxy and/or authentication sections are greater than 50 characters. The length of the username field is limited to 50 characters maximum.
 
User-added image
Resolution
When using a SOAP web service node, if using the proxy and/or authentication fields, use a username in the proxy and authentication fields of 50 characters or less.

Related Articles

Trending Articles

Don't see what you're looking for?