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
Expand all | Collapse all

Consumer WSD connector(WS Security implementation using Policy)

  • 1.  Consumer WSD connector(WS Security implementation using Policy)

    Posted Wed June 19, 2019 09:20 AM

    I would like to know that, how to pass run time values like time stamp, token to webservice connector when we are implementing webservice security by using policies(out of box policies or built in policies)?

    <o:Security s:mustUnderstand=“1” xmlns:o=“http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd”>
    <u:Timestamp u:Id=“_0”>
    <u:Created>2016-06-10T04:23:53.138Z</u:Created>
    <u:Expires>2016-06-10T04:28:53.138Z</u:Expires>
    </u:Timestamp>
    <o:UsernameToken u:Id=“xxxxxxxxxxxxxxxxxxx”>
    <o:Username>abc</o:Username>
    <o:Password o:Type=“http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile1.0#PasswordText”>xxxx</o:Password>
    </o:UsernameToken>
    </o:Security>

    I have to send above security information in the soap header using policy, we have created out of box policy with user name,password and we have a chance to pass values to them via connector. But how pass run time values for ‘Created’ and ‘Expires’ timestamp and u:Id?

    Could you please suggest me?


    #API-Management
    #webMethods
    #soa


  • 2.  RE: Consumer WSD connector(WS Security implementation using Policy)

    Posted Thu June 27, 2019 04:51 PM

    timestampes are generated automatically.
    it’s taking the local time and with the setting from your Web Service Provider Endpoints
    you can set it at:
    Settings > Web Services
    Timestamp Time to Live (seconds)
    U:ID is also auto generated by IS.


    #webMethods
    #API-Management
    #soa