Support Article
Unable to send a SOAP request when using Signature in WSSecurity
SA-31988
Summary
User is using PRPC 6.1 SP2 and are unable to send a SOAP request when using Signature in WS-Security profile.
They are using a custom version of InvokeAxis2 activity.
On enabling signature in WS-Security profile they are getting exception in SOAP connector.
The connector terminates after throws exception is in Step# 7 of their InvokeAxis2 activity and the processing ends after Step #8 where the exception is caught.
Error Messages
com.pega.apache.axis2.AxisFault: WSHandler: Signature: error during message processingcom.pega.apache.ws.security.WSSecurityException: General security error (WSEncryptBody/WSSignEnvelope: Element to encrypt/sign not found: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd, Timestamp)
Steps to Reproduce
- Enable Signature in WS-Security profile.
- Configure Connect-SOAP to use the WS-Security profile configuration using the Advanced tab of connect SOAP Rule. The SOAP Connector fails and exits while sending the outbound request.
Root Cause
An issue in the custom application code or rules is identified as root cause of the issue.
Resolution
Set the following two Dynamic System Setting entries:
1. Purpose : wsa/MustUnderstand
Owning Ruleset : Pega-IntSvcs
Value : false
2. Purpose : wss/MustUnderstand
Owning Ruleset : Pega-IntSvcs
Value : false
Published January 10, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.