Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SOAP headers are mapped incorrectly



Developers have noticed a problem that seems to stem from InvokeAxis2. InvokeAxis2 in Pega-IntegrationEngine : 06-03-15 seems to strip off the header elements.

For example:

SOAP Request XML using InvokeAxis2 activity in Pega-IntegrationEngine : 06-03-15:

<ns2:Security xmlns:ns2=> </ns2:Security>

When it should look like:

<ns2:Security xmlns:ns2="" xmlns:ns1="">

Error Messages

org.xml.sax.SAXParseException: XML document structures must start and end within the same entity
SAML token truncated from the header

Steps to Reproduce

Use a SOAP-connect rule with TLSv1.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. The issue is not in InvokeAxis2, but rather in pzAddCustomHeadersToSoapEnvelope which is called from within InvokeAxis2. The issue is that pzAddCustomHeadersToSoapEnvelope is not properly iterating through the header information that is being parsed to it.


This issue is resolved by hotfix item HFix-21731.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us