On 19 July 2015 at 08:28, acartcat <[email protected]> wrote:
Hi,
> I have the Java Broker 0.32 running and am trying to connect to it from
> a Linux box running proton-c 0.9.1. I have set up the broker with PLAIN on
> 5672 but even when trying to connect using the proton-c example send the
> connection fails at SASL negotiation. The client sends sasl-int(65) with
> PLAIN and a user name and password, the response is sasl-mechanisms(64)
> with CRAM-MD5. I have tried an MD5 on the broker but this has the client
> showing a response of CRAM-MD5-HASHED and CRAM-MD5-HEX.
>
> So, should it be possible to connect to the Java Broker from a Proton-C
> client? Do I need some extra config at either end?
>
The Java Broker does not offer PLAIN authentication over non-SSL ports by
default. It does this to prevent the clear text password travelling over
the wire. You should be able to switch to using SSL, or reenable PLAIN
authentication on non-secure by adding the following attribute/value pair
"secureOnlyMechanisms" : [],
into the configuration for your authentication provider in your
${QPID_WORK}/config.json. E.g.
{
"id" : "ef78d9a3-7011-459f-8a53-2e91d3bf30da",
"name" : "passwordFile",
"secureOnlyMechanisms" : [],
"path" : "${qpid.home_dir}/etc/passwd",
"type" : "PlainPasswordFile",
"preferencesproviders" : [ {
"id" : "db265e14-c9d2-4fca-8f77-ae4c2bcf9203",
"name" : "fileSystemPreferences",
"path" : "${qpid.work_dir}/user.preferences.json",
"type" : "FileSystemPreferences"
} ]
}
>
> Cheers
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/Proton-C-Client-To-Qpid-Java-Broker-SASL-Mechanisms-tp7628337.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
