*Hi Jakub,* Thank you for explaining the chrome related issue. Basically, my application will run as a console application rather like a service but I will discuss with the server/broker side regarding the CA and Trusted Peer thing you mentioned.
*Hi Cliff, * Unfortunately, the server (broker) side is not developed by us and I guess it is not even developed in windows. I also know that the client certificate support is not implemented in Windows implementation of the Qpid client. Therefore, I am trying to modify the API code to add this client certificate support. I am doing this by looking at the server/broker implementation. Uptil now, I have modified the ctor of the /"SslConnector"/ class to open certificate store /"CertOpenStore"/ and to find the certificate /"CertFindCertificateInStore"/ before it tries to /"AcquireCredentialsHandle"/ in /"SSLConnector.cpp"/. It can open the store successfully and finds the certificate as well and even goes to /"ClientSslAsynchIO::startNegotiate()"/ but when it comes to /"ClientSslAsynchIO::negotiateStep(BufferBase* buff)"/ it fails while trying to /"InitializeSecurityContext"/ and goes to/ "negotiationFailed"/ and gives the following error; /2012-01-25 18:08:09 notice SSL negotiation failed to <server-ip>:10170: The target principal name is incorrect./ Please let me know, if I have missed anything to modify or if this is not the right way to add the certificate support for the client side. Many thanks. -Hamid. -- View this message in context: http://qpid.2158936.n2.nabble.com/warning-Connect-failed-tp7229984p7242637.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]
