App Connect

App Connect

Join this online user 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.


#Applicationintegration
#App Connect
#AppConnect
 View Only
  • 1.  Digital Signature

    Posted Tue June 03, 2014 06:01 AM
    Hello every one
    I am trying to create the digital signature using the policy set, this digital signature should be signed inside the body of the envelope NOT inside the header.
    after doing the configuration of creating the certificate and configured the trust store and the private key (with the knowledge that the broker installed on AIX server), i followed the steps of configuration the policy set and the policy binding on the info center.
    but when I deployed the flow, it stopped at the SOAP request node, then an exception occurred because the timeout of the web service it self
    I am sure that the policy set did not configured correctly.

    Can any one help me of how to make the broker do the digital signature part, with considering the following points:
    1. my flow contains a soap request node which consumed a WCF web services (web services from microsoft), with the knowledge that i configured the WS-RM and it worked correctly.
    2. I need to sign the signature inside the body of the SOAP envelope, with the knowledge that the xpath of the signature have 2 fields contains a name space (Envelope, Body, ns1:Inquire,ns2:InquiryRequest) then send it to the web service
    3. what is the needed security items is needed (private key, trust store, etc...)
    4. X509 is needed
    5. If I want to verify the digital signature on the response message, what is the needed steps?
    6. It is impossible to create a new certificate.

    Thanks for help


  • 2.  RE: Digital Signature

    Posted Sat February 13, 2016 03:54 PM

    What you are looking for is a custom message that has nothing to do with the WSS standard.

    According to wss standard the signature is done as per the output created with the policy set. (Same thing for encryption).

    For your custom setup you will need to write some code...