Using WS-Security in Connect SOAP causes failure
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.
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
com.pega.apache.axis2.AxisFault: Transport error: 404 Error: Not Found
Steps to Reproduce1. Create a connect SOAP rule.
2. Add a WS-Secuirty profile that includes a username and password.
3. Click the Test connectivity button.
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.
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.
0% found this useful