On 10/29/2013 12:18 AM, Albert Pomortsev wrote:
Hello qpid developers and users.I'm finding it impossible to use SSL from .NET messaging API. I built qpid/proton from trunk sources on Windows. I can successfully run the broker and, for example, run the csharp.example.helloworld .NET sample using both amqp 0-10 and 1.0 protocols. But configuring the client connection for SSL fails. By SSL I mean only server authentication and encryption, not client authentication. I was planning to use PLAIN SASL authentication with SSL. The C++ broker handbook states (p.42): 3. To open an SSL enabled connection in the Qpid Messaging API, set the protocol connection option to ssl. This does not work. I'm receiving the exception "Unsupported protocol: ssl". Additionally, this option clashes with the option "protocol:amqp1.0" making using them together apparently impossible. I tried "transport:ssl". With amqp 0-10 (no "protocol" option) I'm getting "Failed to connect (reconnect disabled)" exception. With amqp1.0 ("protocol:amqp1.0") I'm getting "No such transport: ssl" exception.
The 'transport' option is what is needed. The protocol option refers to AMQP 1.0 v AMQP 0-10 as you state.
Can someone please explain: - Is SSL even supported in .NET messaging API?
It should be for 0-10, but unfortunately it is not yet for 1.0 on windows.
- If yes, what is the correct way to enable it?
There is a text document in the root of the cpp source tree: https://svn.apache.org/repos/asf/qpid/trunk/qpid/cpp/SSL, which in the second half describes how to get windows working from c++ and I believe the same configuration options will work for .NET (using 0-10).
Did you already specify these? If so, were there any errors on the broker side when connecting over 0-10 and ssl? The error you got there is a fairly generic one. Turning up the log level on the client may also help.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
