Connect SOAP throwing exception while consuming external Service
Connect SOAP in PRPC 6.2 SP2 based application throws an exception due to “actions mismatch” while consuming SOAP Service.
com.pega.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed (actions mismatch)
Steps to Reproduce
Connect to an external SOAP Service using Connect SOAP rule with WS-Security enabled.
The root cause of this issue was “Timestamp” not mentioned in Inflow of Security Profile. The response received from the external SOAP Service had Timestamp in the security header.
Adding Timestamp in Inflow of Security Profile resolved the issue.
0% found this useful