Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to send a SOAP request when using Signature in WSSecurity



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 General security error (WSEncryptBody/WSSignEnvelope: Element to encrypt/sign not found:, Timestamp)

Steps to Reproduce

  1. Enable Signature in WS-Security profile.
  2. 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.


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

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us