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

Must Understand check failed for custom SOAP header

SA-26023

Summary



For a Service call with a custom SOAP Header, the user gets the error Must Understand check failed for Custom SOAP header. The same request is successful with the SOAP UI. 


Error Messages



Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security

Steps to Reproduce



Create a Service call with a custom SOAP Header.

Root Cause



The SOAP Connect rule is implemented using a SOAP header without a namespace.

Resolution



Specify the Dynamic System Setting:
Owning ruleset: Pega-IntegrationEngine
Purpose: DisableMustunderstandHeader
Value: true

Published September 21, 2018 - Updated October 8, 2020

Was this useful?

33% 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