On 02/25/2015 06:40 PM, Andrew Stitcher wrote:
On Wed, 2015-02-25 at 10:27 +0100, Jakub Scholz wrote:
I understand the idea and I would even agree that this is the proper way
how to do it in the long term. But I'm not sure whether all brokers support
this concept. For example, I'm not sure whether you can configure the Qpid
C++ broker in a way to accept AMQP 1.0 connections with SSL Client
Authentication without SASL EXTERNAL while at the same time accepting AMQP
0-10 connections only with SASL EXTERNAL. Therefore I would be afraid that
allowing SSL Client Authentication only without SASL could cause some
serious incompatibilities - I think both should be possible / supported.
And both are supported.
The qpidd 0-10 support is not going to change. The qpidd 1.0 support is
on a different code path so there is little bleed over in functionality.
Also, for the sake of clarity, the qpidd 1.0 SASL support does not use
proton anyway at present (neither does the qpid::messaging c++ client),
so this doesn't change the 1.0 path either.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
