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

Using WS-Security in Connect SOAP causes failure

SA-12508

Summary



SOAP call fails when a WS-Security profile is added in the Advanced tab of the Connect-SOAP rule. If WS-Security is unchecked and then the Security header is hard coded on the Request tab as a header, then it works.


Error Messages



2015-07-06 05:43:41,593 [    WebContainer : 5] [  STANDARD] [                    ] [      THISFW:01.01.11] (      internal.mgmt.Executable) ERROR server.com|Rule-Connect-SOAP.THISFW-SOAP-Service User - Exception
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed

Caused by:
com.pega.apache.axis2.AxisFault: Transport error: 404 Error: Not Found


Steps to Reproduce

1. Create a connect SOAP rule.
2. Add a WS-Secuirty profile that includes a username and password.
3. Click the Test connectivity button.


Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules. If WS-Security is enabled, the header is not added to the SOAP envelope unless WS-Addressing is also enabled.

Resolution



This issue is resolved by performing the following local-change:

Configure and enable WS-Addressing to allow the header to be generated correctly, allowing the SOAP call to complete successfully.

Published July 30, 2015 - 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