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.



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
  • 1.  Does webMethods support SHA1 encryption/signing for SOAP security policy

    Posted 12/17/14 11:48 AM

    My client is using SHA1 for their signing/encryption policy of their webservice (in the SOAP security header). Is there a way to use SHA1 for the security policy, as it seems wm uses SHA2.

    Thanks!
    Will


    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 2.  RE: Does webMethods support SHA1 encryption/signing for SOAP security policy

    Posted 12/17/14 02:42 PM

    you can customized the policy file to use other AlgorithmSuite
    You can find the policy file at:
    \IntegrationServer\instances\default\config\wss\policies

    start with an existing policy.
    edit this field:
    sp:AlgorithmSuite
    wsp:Policy
    <sp:TripleDesRsa15 />
    </wsp:Policy>
    </sp:AlgorithmSuite>
    you can find all possible Algorithm Suite at:
    http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/ws-securitypolicy-1.2-spec-os.html#_Toc161826547
    section 6.1, most basic ones are using SHA1


    #B2B-Integration
    #webMethods
    #Integration-Server-and-ESB


  • 3.  RE: Does webMethods support SHA1 encryption/signing for SOAP security policy

    Posted 12/17/14 02:57 PM

    Thanks. I just went through all the SHA1 algorithms and still get “signature or decryption was invalid.”


    #webMethods
    #Integration-Server-and-ESB
    #B2B-Integration


  • 4.  RE: Does webMethods support SHA1 encryption/signing for SOAP security policy

    Posted 12/18/14 03:53 PM

    Check with your client for the value they use in the AlgorithmSuite field.
    SHA1 is only part of the Suite. They may be using a different one.

    For that error, it may caused by a missing cert configuration (you don’t trust the cert that’s signing or encrypting the message). Have you configure client cert for Message Authentication, Verify and Encrypt


    #Integration-Server-and-ESB
    #B2B-Integration
    #webMethods