Support Article
HFIX-6912 is not working with existing WS Security profile
SA-380
Summary
User's SOAP service that utilizes a different means of security - WS Security - is broken. InvokeAxis2 is not correctly building a soap envelope when WS Security is enabled. The resulting error is "SOAP Envelope can not have children other than SOAP Header and Body". If the WS Security profile is removed from the SOAP Connector, the service responds with "WSDoAllReceiver: Incoming message does not contain required Security header ".
Error Messages
1B. "SOAP Envelope can not have children other than SOAP Header and Body "
2B. "WSDoAllReceiver: Incoming message does not contain required Security header"
Steps to Reproduce
1A. Execute soap service (w/ WS Security Profile) calling activity against Activity InvokeAxis2 in Pega-IntegrationEngine:06-02-25.
1B. Note Error
2A. Execute soap service (w/out WS Security Profile) calling activity against Activity InvokeAxis2 in Pega-IntegrationEngine:06-02-25.
2B. Note Error
Resolution
Enable WS-Addressing box needs to be checked in the SOAP Connect rule if enabling WS-Security.
Published March 11, 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.