On 06/25/2015 10:18 AM, Robbie Gemmell wrote:
Looks good to me. Anyone else think otherwise?
looks good to me also
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Looks good to me. Anyone else think otherwise?
Robbie
On 23 June 2015 at 17:41, Lorenz Quack wrote:
> The general consensus seems to be that the docs should change and reflect
> that:
> * the available mechanisms changes with the underlying transport and
> * this can be influenced by setting s
The general consensus seems to be that the docs should change and
reflect that:
* the available mechanisms changes with the underlying transport and
* this can be influenced by setting secureOnlyMechanisms in the
config.json.
I created QPID-6606 and attached a patch with a suggested wording.
On 06/12/2015 04:54 PM, Rob Godfrey wrote:
On 12 June 2015 at 17:45, Gordon Sim wrote:
On 06/12/2015 10:48 AM, Rob Godfrey wrote:
The documentation doesn't tend to go into the detail of the SASL
mechanisms available from each provider (and how they may differ
between TLS and non-TLS)... and f
On 12 June 2015 at 17:45, Gordon Sim wrote:
> On 06/12/2015 10:48 AM, Rob Godfrey wrote:
>>
>> The documentation doesn't tend to go into the detail of the SASL
>> mechanisms available from each provider (and how they may differ
>> between TLS and non-TLS)... and from a general user perspective I'm
On 06/12/2015 10:48 AM, Rob Godfrey wrote:
The documentation doesn't tend to go into the detail of the SASL
mechanisms available from each provider (and how they may differ
between TLS and non-TLS)... and from a general user perspective I'm
not sure that would be useful.
I think it is useful to
On 12 June 2015 at 10:48, Rob Godfrey wrote:
> On 12 June 2015 at 11:18, Robbie Gemmell wrote:
>> I tend to disagree. The option exists, and seems about as useful (if
>> obviously slightly different) as e.g. being able to enable the
>> ANONYMOUS authentication provider. Having it written down som
On 12 June 2015 at 11:18, Robbie Gemmell wrote:
> I tend to disagree. The option exists, and seems about as useful (if
> obviously slightly different) as e.g. being able to enable the
> ANONYMOUS authentication provider. Having it written down somewhere
> other than a mailing list would make answe
I wasn't suggesting it needs to be in the UI, although I wouldnt have
a problem if it were given that it would be burried away deep in the
options (like the one to enable basicAuth of HTTP was).
I dont think adding a snippet about editing the JSON in the depths of
the broker docbook is making it p
I tend to disagree. The option exists, and seems about as useful (if
obviously slightly different) as e.g. being able to enable the
ANONYMOUS authentication provider. Having it written down somewhere
other than a mailing list would make answering this type of question
simpler in future (or avoid it
I'm minded to agree - certainly I don't think we want to make it easy
(via the UI for example) to enable this inherently insecure
configuration. The problem at the moment is that proton seems to have
very limitted abilities with respect to SASL, and clients seem to
either use PLAIN, or omit the SA
I'm not sure this should be in the docs. I would not encourage people to
send password in the clear over a network.
Lorenz
On 11/06/15 17:37, Robbie Gemmell wrote:
Can this be added to the documentation to make it easier to point
people at, and make it better known? Assuming it isnt already t
Ok, with AMQP 0-10 things seems to be working fine except for python
not able to use credentials. To be able to connect from qpid-python I
have to enable anonymous provider.
On Thu, Jun 11, 2015 at 8:37 PM, Robbie Gemmell
wrote:
> On 11 June 2015 at 16:09, Mansour Al Akeel wrote:
>> I restarte
On 11 June 2015 at 16:09, Mansour Al Akeel wrote:
> I restarted the server, but still no juice !
> is there a way I can tell proton to use AMPQ 0-9 or 0-10 ?
>
No, Proton only supports AMQP 1.0
> I think reverting back to a previous version should solve my problems for now
> !
>
>
>
> On Thu, J
Can this be added to the documentation to make it easier to point
people at, and make it better known? Assuming it isnt already that is,
I had a peek for the 0.32 docs but didnt see it.
Robbie
On 11 June 2015 at 16:20, Lorenz Quack wrote:
> Hi Mansour,
>
> if you want to connect with SASL PLAIN
Hi Mansour,
if you want to connect with SASL PLAIN on a unsecured connection (which
is obviously not recommended). you need to tell the to allow this.
You can do this by setting
"secureOnlyMechanisms" : [ ]
in the plain authenticationProvider section in your config.json file.
It should then lo
I restarted the server, but still no juice !
is there a way I can tell proton to use AMPQ 0-9 or 0-10 ?
I think reverting back to a previous version should solve my problems for now !
On Thu, Jun 11, 2015 at 6:52 PM, Gordon Sim wrote:
> On 06/11/2015 03:28 PM, Mansour Al Akeel wrote:
>>
>> Gor
On 06/11/2015 03:28 PM, Mansour Al Akeel wrote:
Gordon,
thank you.
I added Both Anonymous and PLAIN. Here's the steps to add them from
the httpManagement console:
-Double click "Broker" folder. Go to "Authentication Providers", and click add.
-Fill the current information:
Name: anonymous
Type: A
Gordon,
thank you.
I added Both Anonymous and PLAIN. Here's the steps to add them from
the httpManagement console:
-Double click "Broker" folder. Go to "Authentication Providers", and click add.
-Fill the current information:
Name: anonymous
Type: Anonymous
-Then did it again for Plain:
Name: PLAI
On 06/11/2015 01:41 PM, Mansour Al Akeel wrote:
SaslMechanisms{saslServerMechanisms=[CRAM-MD5]}
That looks like the broker is only configured to support CRAM-MD5 which
proton as of 0.9.1 does not support (it hopefully will from 0.10).
You would need to enable PLAIN or ANONYMOUS to allow the
I tried with admin:admin@localhost:5672
I am getting error:
python2.7:
/tmp/pip_build_root/python-qpid-proton/build/bundled/qpid-proton/proton-c/src/transport/transport.c:1599:
transport_consume: Assertion `n == (-1)' failed.
Aborted
On the broker side:
2015-06-11 16:30:17,514 INFO [IoReceiver
On 06/11/2015 01:01 PM, Mansour Al Akeel wrote:
Hello,
I have Qpid java broker 0.32.
Installed python-qpid-proton 0.91 from pip using "pip install
python-qpid-proton" (thank you for adding it to python packages)
I created a queue called "examples".Then downloaded
qpid-proton-0.9.1.tar.gz to o
22 matches
Mail list logo
