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

Connect SOAP fails with to "WS-Security"



When running an activity which invokes a Connect SOAP Rule that has a Username Configuration Type WS-Security profile, the SOAP service fails with errors in the log.

Error Messages SOAP service failed
Caused by: 
Internal Error.  
Domain name: <DOMAIN NAME>
Process type: Multiprotocol 
Gateway Name: <GATEWAY NAME>                            
Error message:    Rejected by policy.
Stack trace:  
Rejected by policy. while processing service <SERVICE> and rule <RULE NAME>-policy_rule_error.  
Service error code is 0x00d30003.  Transaction Id is XXXX.
Service error header is HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
X-Backside-Transport: FAIL FAIL
Connection: close

Steps to Reproduce

Enable WS-Security for the Connect SOAP Rule then run the activity to invoke the Connect SOAP Rule.

Root Cause

The root cause of this problem is a configuration error.


There use the following local-change: Enable the WS-Addressing option in the Connect SOAP rule so Pega will process the routing information and include it in the SOAP header.

Published March 10, 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