IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  WS Security Handler - Header element properties not accessible

    Posted Wed January 13, 2010 12:50 PM

    Hi all,

    I have configured a Web Service Consumer (WSD) following the step described in “7.1.1_Web_Services_Delevoper_Guide.pdf” using WS Security capabilities and policy files.

    When running WS Consumer following SOAP-FAULT is returned :

    faultcode :soapenv:MustUnderstand
    faultstring:Did not understand “MustUnderstand” header(s):{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security

    I am unable to modify the mustunderstand property (to false) as WS Security Handler - Header element properties is not accessible on Developer.

    Appreciate any feedbacks.

    Kind Regards,
    Djibril.


    #soa
    #API-Management
    #webMethods


  • 2.  RE: WS Security Handler - Header element properties not accessible

    Posted Wed January 13, 2010 03:58 PM

    As per link below the problems is apparently in Axis side (web service provider).

    [url]http://wso2.org/library/tutorials/understand-famous-did-not-understand-mustunderstand-header-s-error[/url]

    Axis doesn’t handle mustunderstand attribute.

    Does anyone know how can i suppress the mustunderstand attribute in WS Security SOAP Header in webMethods 7.1.2 ?

    Thanks,
    Djibril.


    #webMethods
    #API-Management
    #soa


  • 3.  RE: WS Security Handler - Header element properties not accessible

    Posted Fri January 15, 2010 03:09 PM

    Using a custom SOAP Handler will give you full access to all aspects of the SOAP Header and Body, so you can customise the payload XML to work round any issues.


    #webMethods
    #API-Management
    #soa


  • 4.  RE: WS Security Handler - Header element properties not accessible

    Posted Fri January 15, 2010 09:42 PM

    Thanks for your reply.

    That’s what i finally did in some way. I reused a previous 6.5 WS Connector and added a document-based WS Security header using addHeaderEntry service.

    However I still don’t now how to suppress the mustUnderstand tag in 7.1.2 WSD, bug or product bad design. This is webMethods.

    Thanks again.
    Regards,
    Djibril.


    #webMethods
    #API-Management
    #soa


  • 5.  RE: WS Security Handler - Header element properties not accessible

    Posted Sun September 25, 2011 05:35 PM

    Djibril,

    I am trying to change the mustUnderstand to “0” from the default value of “1” too. Have you or anyone resolve this problem?

    Thanks,
    Tat


    #soa
    #webMethods
    #API-Management