Hi Steve, Thank you for your reply.
> Did you use https://broker-addr:5671 ? > (If you use http:// it would probably act as you observed) Indeed I haven't thought of https, and you are exactly right, it works. I only doubted the broker configuration and format of the client certificate because I was having various authentication problems. > Which C# client are you using, from which qpid version? I am using a C# client from qpid-0.6 and yes, the SSL support wasn't enabled in it. Which is why I couldn't get it to work without changing the client's source code. I finally got it to work. Just in case somebody else is out there looking for answers to the same questions. I found out that for SSL encrypted connection C# client internally uses .NET SslStream's AuthenticateAsClient() method, which takes X509 certificates in DER (binary) format. In my case broker was configured for SASL EXTERNAL authentication mechanism. Client certificate had to have both public and private keys. C# client uses PLAIN mechanism by default so I had to extend Client.Connect*() methods to support different SASL mechanisms. Also when using EXTERNAL mechanism username and password shouldn't be sent, I presume those are taken from the certificate, otherwise connection fails. Steve, thank you for being so helpful. Kind regards, Elena -- View this message in context: http://n2.nabble.com/SSL-and-C-client-anyone-have-a-complete-example-tp4030718p4872632.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]
