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

Server certificate rejected by ChainVerifier using useridpwd authentification

  • 1.  Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Mon April 28, 2003 03:43 PM

    Trying to connect to a webMethods marketsite the following error is thrown:
    SSL v3 Toolkit enabled Encryption Ciphers:
    SSL_RSA_EXPORT1024_WITH_DES_CBC_SHA
    SSL_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA
    SSL_RSA_EXPORT1024_WITH_RC4_56_SHA
    SSL_DHE_DSS_EXPORT1024_WITH_RC4_56_SHA
    SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
    SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
    SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
    SSL_DH_RSA_EXPORT_WITH_DES40_CBC_SHA
    SSL_DH_DSS_EXPORT_WITH_DES40_CBC_SHA
    SSL_RSA_EXPORT_WITH_RC4_40_MD5
    SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5
    SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA
    SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
    SSL_RSA_WITH_NULL_SHA
    SSL_RSA_WITH_NULL_MD5
    Verifying peer certificate chain.
    com.commerceone.xdk.excp.metadox.send.TransferException: Error while silently connecting: org.w3c.www.protocol
    .http.HttpException: iaik.security.ssl.SSLException: Server certificate rejected by ChainVerifier
    at com.commerceone.ccs.comm.sender.http.HttpTransmitter.sendEnvelopeReceiveEnvelope(HttpTransmitter.java:193)
    at com.commerceone.ccs.comm.sender.http.HttpTransmitter.handleDocument(HttpTransmitter.java:262)
    at com.commerceone.ccs.comm.sender.https.HttpsTransmitter.handleDocument(HttpsTransmitter.java:383)

    Any information would be greatly appreciated.

    thanks.


    #webMethods
    #Integration-Server-and-ESB
    #webMethods-Archive


  • 2.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Thu June 12, 2003 11:27 PM

    I assume you are trying to establish a https session with the remote server. I believe this error is occuring during the SSL session handshaking setup. I think you will find that the “Server certificate rejected by Chainverifier” message is caused by your IS not being able to verify the signature of the server certificate (Public key) of the remote server. That is, you do not have the Certificate Authority Root certificates (CA Root certificates) that signed the servers public key cert installed in your IS. You can either ask the remote server’s operators for copies of the appropriate CA Root certs or if you can obtain their public key cert you can extract the CA Root certs from that or at least determine who the signing CA is. Once you get the CA Root certs place them in the directory defined on “Trusted Certificates” (or something like that - It is on the administrator|Certificates page). It is my experience that you must then restart IS to “activate” the new CA Root certs.


    #webMethods-Archive
    #Integration-Server-and-ESB
    #webMethods


  • 3.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Wed September 17, 2003 02:28 PM

    I had the same problem. After reading John’s message I checked the certificates. Somehow some very strange root certificates were installed, completely not matching (RSA 1024 bits vs. 512 bits) with the client certificate. After instelling the gooed root certificate the problem was solved.


    #webMethods-Archive
    #webMethods
    #Integration-Server-and-ESB


  • 4.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Tue February 10, 2004 03:06 AM

    I’m currently getting this error. I don’t have the server’s CA Root Certificate in the “CA Certificate Directory”, but the Admin guide states that if you don’t specify a “CA Certificate Directory” it will trust all server certificates. I’ve always seen it work like this as well.

    It works from the IE browser just fine. Doesn’t wm come with a file that contains the trusted root authorities. I remember editing this a few years back…

    Any ideas?


    #webMethods-Archive
    #webMethods
    #Integration-Server-and-ESB


  • 5.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Tue February 10, 2004 07:29 PM

    Your IE browser may contain certificates that webMethods does not. webMethods won’t trust “all server certificates”, just whatever standard root certificates it comes with. I don’t have an exact list of which ones webMethods has - anyone know where that’s stored?

    I ran into this exact same problem recently and it turned out that the IE installation I was using had several non-standard certificates. We ended up exporting the certificates from IE and putting them on the webMethods server, then setting the CA Certificate Directory. Of course, that meant we also had to export all the standard certificates that we needed and put those in that same directory.


    #webMethods-Archive
    #webMethods
    #Integration-Server-and-ESB


  • 6.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Wed April 07, 2004 09:58 PM

    We had this problem and solved by specifying the intermediate cert as the servers root cert instead of CA’s Root cert.der

    Thanks


    #webMethods-Archive
    #Integration-Server-and-ESB
    #webMethods


  • 7.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Fri December 17, 2004 11:18 AM

    is it not possible to ‘switch’ off the certifcate checking?


    #Integration-Server-and-ESB
    #webMethods
    #webMethods-Archive


  • 8.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Fri December 12, 2008 09:26 AM

    Hi I am receving the below error:
    [SIZE=3][COLOR=#000080]Service : wm.server.flow:stepFlow
    Doc Id : N/A
    errorMessage=iaik.security.ssl.SSLException: Server certificate rejected by ChainVerifier

    Can anyone help me out in resolving this issue.
    [/color][/size]


    #Integration-Server-and-ESB
    #webMethods
    #webMethods-Archive


  • 9.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Fri December 12, 2008 11:40 AM

    What version of what product from what vendor are you using? Assuming you mean webMethods IS 7.1.x, be sure that you have applied the latest fixes. If you are using TN you may not have the proper certificate from your trading partner.

    Having done that, the issue could be that your server’s security certificate is not properly formed or that it or its CA authority are not trusted by the server with which you are communicating.

    Google that error to see other details.

    M


    #Integration-Server-and-ESB
    #webMethods-Archive
    #webMethods


  • 10.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Tue June 09, 2009 07:37 PM

    Hi All,

    One of our client use webMethods to call to our webservices hosted in IIS 6. Recently we changed our certificate vendor. After then onwards they are getting the following error

    Error:
    java.io.IOException: iaik.security.ssl.SSLException: Server certificate rejected by ChainVerifier.

    Can any body help me on this.


    #webMethods-Archive
    #webMethods
    #Integration-Server-and-ESB


  • 11.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Sat December 05, 2009 11:19 AM

    Hi Krishna,
    After changing your certificate vendor did you provide your new certificate public key (Complete chain) to your client? If not then provide your new certificate to the client and ask him to configure it on his trusted CA certs (mainely Root and intermideate) and restart his IS server and then try connecting to your application.
    Regards,
    Vikas


    #webMethods-Archive
    #Integration-Server-and-ESB
    #webMethods


  • 12.  RE: Server certificate rejected by ChainVerifier using useridpwd authentification

    Posted Mon December 14, 2009 08:55 PM

    SSL world… always the issue is a bad certificate setup.

    Sometomes to overcome them you canse to true the following:

    watt.security.cert.wmChainVerifier.trustByDefault
    watt.security.ssl.client.ignoreEmptyAuthoritiesList
    watt.security.ssl.ignoreExpiredChains

    Good luck :smiley:


    #Integration-Server-and-ESB
    #webMethods-Archive
    #webMethods