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

WSDoAllReceiver: Request does not contain required security head



You have configured Connect-SOAP with SSL to connect to an external Web service.
When sending a request from the PRPC server, you see this exception:
WSDoAllReceiver: Request does not contain required security header.
Pega 7.1.6 does not generate the security header using the configuration defined in the security profile on the advance tab of the Connect-SOAP rule.

Error Messages

[Application_Ruleset_Version] ( internal.mgmt.Executable) ERROR server_name|ip_address_userID - Exception
2014-09-03 16:45:11,940 INFO [stdout] (Dispatcher-Thread-79) SOAP service failed
2014-09-03 16:45:11,940 INFO [stdout] (Dispatcher-Thread-79) at com.pegarules.generated.activity.ra_action_invokeaxis2_fba00e06130dd4c847512b6d7cb0141b.step15_circum0(
2014-09-03 16:45:11,940 INFO [stdout] (Dispatcher-Thread-79) at . . .

Steps to Reproduce

  1. Create a Connect-SOAP rule that is SSL with username token.
  2. Create a security profile to be configured in the Connect-SOAP rule.
  3. Create a keystore to configure in the security profile.
  4. Call the Connect-SOAP rule from the Connect activity.
  5. See the error message: WSDoAllReceiver: Request does not contain required Security header exception is thrown.

Root Cause

The SOAP Header information is not getting passed in the request through the SOAP Envelop.


Enable WS-Addressing to pass the header content.
Refer to the Pega 7.1.6 Help topic,

Published January 31, 2016 - 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