Skip to Content
avatar image
Former Member

Peer certificate rejected by ChainVerifier

Hi,

I am trying to access a https type service. It involves username and password which i have given in the receiver soap adapter. (using a soap to soap synchronous scenario)

I have imported the server's certificate in the TrustedCA's keystore so that it is accessible. But while testing it, I receive an error "Peer certificate rejected by ChainVerifier".

What may be the issue?

Kindly guide me.

Regards,

Kevin

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

7 Answers

  • Best Answer
    Aug 11, 2008 at 11:26 AM

    can you confirm if the certificates common name (CN) matches the url/host name you are trying to hit?

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 11, 2008 at 10:34 AM

    Make sure u have imported the entire CA hierarchy of your server certificate into the list of trusted CA's in XI.

    Regards,

    Prateek

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 11, 2008 at 11:25 AM

    can you confirm if the certificates common name (CN) matches the url/host name you are trying to hit?

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 11, 2008 at 11:25 AM

    can you confirm if the certificates common name (CN) matches the url/host name you are trying to hit?

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 11, 2008 at 11:25 AM

    can you confirm if the certificates common name (CN) matches the url/host name you are trying to hit?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 17, 2012 at 12:33 PM

    I know this thread is old, but recently I had the same error message but a very different and maybe disturbing solution:

    All keys were correct in a SAP -> PI -> SOAP scenario with a user authentification. The reason for the error was in the typing of the user name which had to be in lower case for the connecting service, but I was using it in upper case.

    Add comment
    10|10000 characters needed characters exceeded

  • May 24, 2013 at 02:39 PM

    I experienced the same problem.

    The solution for my problem was to add a parameter   strictHostnameChecking  with a value  false     under the Advanded tab - advanced mode - additional parameters   in the communication channel.

    Add comment
    10|10000 characters needed characters exceeded