Support Article
Connect SOAP throwing exception while consuming external Service
SA-7517
Summary
Connect SOAP in PRPC 6.2 SP2 based application throws an exception due to “actions mismatch” while consuming SOAP Service.
Error Messages
com.pega.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed (actions mismatch)
at com.pega.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.java:344)
Steps to Reproduce
Connect to an external SOAP Service using Connect SOAP rule with WS-Security enabled.
Root Cause
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.
Resolution
Adding Timestamp in Inflow of Security Profile resolved the issue.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.