Incorrect building of HTTP header in SOAP condiguration file

Document ID : KB000086251
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
==========================================================================================================

After save the wsdl config in UVC the header part in the ws_soap_services.xml will look like that:

<Headers>
<Header key="Basic VGVzdGVyOnRlc3Q=" value="Basic VGVzdGVyOnRlc3Q=" hiveInternals:__hiveAttributesTypes__="key=java.lang.String;value=
java.lang.String"/>
</Headers>
============================================================================================================

In the HTTP Response (Job log of the SOAP Uproc:

<soap:Body>
<soap:Fault>
<faultcode>soap:MustUnderstand</faultcode>
<faultstring>MustUnderstand headers: [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood.</faultstring>
</soap:Fault>
</soap:Body>

============================================================================================================ 

Patch level detected:Univiewer Console 6.5.01
Product Version: Dollar.Universe 6.5.01

Description :If it is necessary to set a HTTP header in SOAP wsdl configuration File from UVC, the values are not correctly inserted in ws_soap_services.xml file. The header is then incorrect or corrected and executed SOAP uprocs can then abort with an error message:
Environment:
OS: All
Cause:
Cause type:
Defect
Root Cause: N/A
Resolution:
If the upgrade solution is not applicable, there is a Workaround:

===========================================================================
Edit manually the ws_soap_services.xml and set there the correct KEY and VALUE parameter and never insert or modify the header part of the wsdl file from the SOAP Manager Settings in the UVC!!
============================================================================

Fix Status: Released

Fix Version(s):
Component: Univiewer.Console
Version: Dollar.Universe 6.6.04
Additional Information:
Workaround :
N/A