Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Dissanayake A . A . Chamil Jayanth (CHAMILDIS)
Wells Fargo
US
CHAMILDIS Member since 2008 4 posts
Posted: Sep 11, 2018
Last activity: Sep 19, 2018
Posted: 11 Sep 2018 17:49 EDT
Last activity: 19 Sep 2018 18:34 EDT
Closed
Solved

Must Understand check failed for header

Hi All,

We are trying to integrate to a third party SOAP service. As the response of the integration we receive below message as pySOAPFaultReason. Any of you know why we receive this error message and fix for the issue.

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

Thanks in advance.

***Edited by Moderator Marissa to update platform capability tags****

To see attachments, please log in.
Data Integration

Posted: 6 years ago
Posted: 12 Sep 2018 11:32 EDT
Dissanayake A . A . Chamil Jayanth (CHAMILDIS)
Wells Fargo
US

Hi inaKh,

  Thanks for the reply. I had looked into this article and tried to find out "DisableMustunderstandHeader" property and "Pega-IntegrataionEngine" rule set in our application. Currently we are in Pega 7.4 and I was not able to find them. This article was published in July 2016 so now don't know pega have changed the rules mentioned in the article. Are you aware of updated rule details or am I missing some thing while following the steps in the article.

Thanks.

To see attachments, please log in.
Posted: 6 years ago
Posted: 19 Sep 2018 18:34 EDT
Dissanayake A . A . Chamil Jayanth (CHAMILDIS)
Wells Fargo
US

Hi inakh,

  I was able to resolve the issue with the steps mentioned in this article. But the rule set name mentioned in the article is wrong (Already submit a suggestion).

Correct rule set name is Pega-IntegrationEngine  . Thanks for your guidance and help.

 

To see attachments, please log in.

Related content:

Related content has not currently been identified for this post.

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

Pega Collaboration Center 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