You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by eric73 <er...@eaton.com> on 2016/08/11 15:24:33 UTC
SSL not working with EXTERNAL mechanism
Hi all,
I’m working on a C++ project developed with Qpid libraries on Linux.
I try to communicate between a qpid broker and a client base on the Qpid C++
messaging API (AMQP 1.0 protocol) with SSL connection.
I use the libraries with the latest version available (make complete
compilation on Linux mint 17.3 distribution and on Windows 7 platform).
-qpid-proton: 0.13.1
-qpid-cpp: 0.34
I test on Linux with the qpid-send and qpid-receive programs.
The programs work correctly with no SSL but if SSL is activated, I have the
error:
I use the following commands on two separate consoles:
Note, the qpid-perfest program work correctly:
I have the same problem if I running client on Windows.
The qpid broker is running on a Windows machine with command (qpidd.conf is
empty):
Any help will be appreciate
Thanks
Regards
--
View this message in context: http://qpid.2158936.n2.nabble.com/SSL-not-working-with-EXTERNAL-mechanism-tp7649077.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
EXTERNAL not supported on windows? (was Re: SSL not working with
EXTERNAL mechanism)
Posted by Gordon Sim <gs...@redhat.com>.
On 16/08/16 15:49, eric73 wrote:
> Hi Gordon,
>
> Thanks for you response, I have the following error:
>
> when I run the following command:
>
Fyi, neither the command nor the error made it through in the mail I
got. I was only able to read them by looking your mail up in nabble. Not
sure how you are including those snippets, but inline text would be better
> I have this error when I'm using SSL authentication of the clients with
> EXTERNAL mechanism.
>
> If I don't specify the EXTERNAL mechanism (just pass {transport:ssl} in the
> connection option), there is no error but I don't think that it is the
> expected behavior ?
From a cursory look at the windows code it looks like EXTERNAL is not
supported there (only PLAIN and ANONYMOUS). Can someone more familiar
with the code there confirm or refute this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: SSL not working with EXTERNAL mechanism
Posted by Gordon Sim <gs...@redhat.com>.
On 17/08/16 07:21, eric73 wrote:
> If I want SSL with a login and a password encrypted for access, I understand
> that it is not possible with EXTERNAL option with QPID broker
Just to clarify, EXTERNAL *is* supported on linux, just not yet on windows.
> but is it possible with PLAIN option ?
Yes, you can use PLAIN over SSL and the password will not be sent in the
clear over the network due to SSL encryption.
> If yes, are the following option correct:
> --connection-options "transport:ssl,login:myLogin,password:myPassword}"
It is 'username' rather than 'login'.
> Second question, if the broker is not QPID but activeMQ broker on Windows,
> is it possible to use EXTERNAL access with client ?
You should probably confirm that on the ActiveMQ list, but I don't
*believe* it supports EXTERNAL as a mechanism with AMQP either: "the
broker accepts plain SASL authentication"[1].
The Qpid Java broker does support EXTERNAL[2] and though I haven't ever
tried it on windows, as it is Java I doubt that would make any difference.
--
[1] http://activemq.apache.org/amqp.html
[2]
https://qpid.apache.org/releases/qpid-java-6.0.4/java-broker/book/Java-Broker-Security.html#Java-Broker-Security-External-Provider
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: SSL not working with EXTERNAL mechanism
Posted by eric73 <er...@eaton.com>.
Hi all,
Thanks for your response.
If I want SSL with a login and a password encrypted for access, I understand
that it is not possible with EXTERNAL option with QPID broker but is it
possible with PLAIN option ?
If yes, are the following option correct:
--connection-options "transport:ssl,login:myLogin,password:myPassword}"
Second question, if the broker is not QPID but activeMQ broker on Windows,
is it possible to use EXTERNAL access with client ?
BR
Eric
--
View this message in context: http://qpid.2158936.n2.nabble.com/SSL-not-working-with-EXTERNAL-mechanism-tp7649077p7649325.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: SSL not working with EXTERNAL mechanism
Posted by Gordon Sim <gs...@redhat.com>.
On 16/08/16 18:04, Cliff Jansen wrote:
> I believe Gordon is right: only PLAIN and ANONYMOUS are supported SASL
> mechanisms on Windows at this time. See
>
> src/qpid/broker/windows/SaslAuthenticator.cpp
Thanks for confirming, Cliff!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: SSL not working with EXTERNAL mechanism
Posted by Cliff Jansen <cl...@gmail.com>.
I also cannot read much of the email content unless I separately visit
the nabble version.
I believe Gordon is right: only PLAIN and ANONYMOUS are supported SASL
mechanisms on Windows at this time. See
src/qpid/broker/windows/SaslAuthenticator.cpp
Cliff
On Tue, Aug 16, 2016 at 7:49 AM, eric73 <er...@eaton.com> wrote:
> Hi Gordon,
>
> Thanks for you response, I have the following error:
>
> when I run the following command:
>
> I have this error when I'm using SSL authentication of the clients with
> EXTERNAL mechanism.
> If I don't specify the EXTERNAL mechanism (just pass {transport:ssl} in the
> connection option), there is no error but I don't think that it is the
> expected behavior ?
>
> Sorry, I don't succeed to execute a qpid broker on my Linux for test. There
> is an error (don't find my certificate) and I don't want to start:
>
>
> Best regards
> Eric
>
>
>
>
>
>
> --
> View this message in context: http://qpid.2158936.n2.nabble.com/SSL-not-working-with-EXTERNAL-mechanism-tp7649077p7649294.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: SSL not working with EXTERNAL mechanism
Posted by eric73 <er...@eaton.com>.
Hi Gordon,
Thanks for you response, I have the following error:
when I run the following command:
I have this error when I'm using SSL authentication of the clients with
EXTERNAL mechanism.
If I don't specify the EXTERNAL mechanism (just pass {transport:ssl} in the
connection option), there is no error but I don't think that it is the
expected behavior ?
Sorry, I don't succeed to execute a qpid broker on my Linux for test. There
is an error (don't find my certificate) and I don't want to start:
Best regards
Eric
--
View this message in context: http://qpid.2158936.n2.nabble.com/SSL-not-working-with-EXTERNAL-mechanism-tp7649077p7649294.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: SSL not working with EXTERNAL mechanism
Posted by Gordon Sim <gs...@redhat.com>.
On 11/08/16 16:24, eric73 wrote:
> Hi all,
>
> I\u2019m working on a C++ project developed with Qpid libraries on Linux.
> I try to communicate between a qpid broker and a client base on the Qpid C++
> messaging API (AMQP 1.0 protocol) with SSL connection.
> I use the libraries with the latest version available (make complete
> compilation on Linux mint 17.3 distribution and on Windows 7 platform).
> -qpid-proton: 0.13.1
> -qpid-cpp: 0.34
>
> I test on Linux with the qpid-send and qpid-receive programs.
> The programs work correctly with no SSL but if SSL is activated, I have the
> error:
>
> I use the following commands on two separate consoles:
>
>
> Note, the qpid-perfest program work correctly:
>
> I have the same problem if I running client on Windows.
>
> The qpid broker is running on a Windows machine with command (qpidd.conf is
> empty):
>
> Any help will be appreciate
There seems to be some lines missing from your email, in particular the
error you are seeing and the commands you are running.
To clarify, you are seeing that when using SSL authentication of the
clients, EXTERNAL is not being offered?
Do you see the same behaviour if the broker is running on linux as well?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org