Hi Hamid, Are you actually using a "Third-Party Root Certification Authority" certificate - e.g. Verisign? Or do you have only a public key of a signed or self-signed certificate? Couldn't that be the problem?
I also agree with Gordon that you should not use the IP address to connect to, but the hostname as mentioned in the certificate used by the broker. You may need to change your hosts file to get the hostname routed to the IP address ... Regards Jakub On Fri, Jan 27, 2012 at 16:36, Hamid.Shahid <[email protected]> wrote: > Hi, > > > I am getting the following error when I try to connect via my client code. > After placing all the certificates in the "Third-Party Root Certification > Authorities" > > 2012-01-25 18:08:09 notice SSL negotiation failed to <server-ip>:10170: The > target principal name is incorrect. > 2012-01-25 18:08:09 warning Connect failed: The target principal name is > incorrect. > (..\..\..\..\..\..\..\..\qpidc-0.12\src\qpid\client\windows\SslConnector.cpp:111) > > Please let me know, what does it mean and how can it be rectified. > > Thank you. > > regards, > Hamid. > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/warning-Connect-failed-tp7229984p7229984.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
