Support Article
SOAP Headers not correctly added when WS Addressing is selected
SA-5948
Summary
We have a SOAP service which is used in authentication process and for this service the Enable ws-addressing is on. However the headers (like action, MessageID ) with addressing information are not added to the SOAP request. Those were getting correctly added with version 7.1.5.
Examples:
In 7.1.7, the SOAP message has:
<soapenv:Header>
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing" />
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing" />
</soapenv:Header>
while the 7.1.5 the SOAP message has:
<soapenv:Header>
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">
http://xxx.xxx.xxx.xxx/xxx.xxx.
</wsa:Action>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">
urn:uuid:91576FE2-4533-43CB-BFA1-51D2B631453A
</wsa:MessageID>
</soapenv:Header>
We have already installed a Hotfix for the normal headers that we received earlier which then fixed the generic problem with the SOAP Headers we faced earlier. This was HFIX-20037.
Error Messages
The SOAP call fails as the Service expects the values in the Header
Steps to Reproduce
Create a Connect SOAP
Enable ws-addressing on Advanced tab and add action and Message ID to it
When the SOAP request is made, the headers are missing
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules and it is a regression issue.
Resolution
This issue is resolved by hotfix item HFIX-20726.
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.