OK - there's that issue... and then there is an authentication problem.
Namely that on trunk the Java Broker does not offer PLAIN authentication
over non-SSL ports by default. It offers CRAM-MD5, SCRAM-SHA1 and
SCRAM-SHA256... but I'm presuming the messenger client doesn't yet
implement any of these.
Connecting over SSL should work... but I wan't having any success with that
either - which warrants investigation.
However, to reenable PLAIN authentication on non-secure connections add the
attribute/value pair
"secureOnlyMechanisms" : [],
into the configuration for you authentication provider in your config.json.
As an example, my password file authentication provider section looks like
this:
{
"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"
}
-- Rob
On 25 August 2014 20:47, Rob Godfrey <[email protected]> wrote:
> Hi Fraser,
>
> the 1-0 support is on by default... The issue may be related to virtual
> hosts... IIRC proton is telling the broker that the host it wants to open
> is "localhost" so if you don't have a localhost virtualhost inside the
> broker then it may fail... The error could obviously do with some work,
> whatever the cause.
>
> I'll try to fire up a fresh broker and clean proton install and see what I
> can see,
>
> Cheers,
> Rob
>
>
> On 25 August 2014 18:37, Fraser Adams <[email protected]>
> wrote:
>
>> Hello,
>> I've just tried using proton's send example with the Java Broker:
>>
>> ./send -a amqp://guest:guest@localhost/amq.fanout
>>
>> and I get the helpful response:
>> [0x21ff810]:ERROR[0] (null)
>>
>> [0x21ff810]:ERROR[0] (null)
>>
>> CONNECTION ERROR connection aborted (remote)
>>
>>
>>
>> I'm pretty sure that I've previously had this working with the Java
>> Broker but I can't think what I'm doing wrong. I can't remember if there's
>> something I need to add to the broker config JSON to make it work with AMQP
>> 1.0, if so what's the incantation I need, if not what am I doing wrong with
>> send?
>>
>> Cheers.
>> Frase
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
