Hi Robbie,
Thanks for that, I have now upgraded to 0.18.
I changed this section
<security>
<pd-auth-manager>
<anonymous-auth-manager/>
</pd-auth-manager>
...
Obviously I gave the java broker a go at digesting the qpid-config stuff... it
persists in answering the same thing :(
Failed: AuthenticationFailure: sasl negotiation failed: no mechanism agreed
As I was not sure what to replace, I also got rid of the pd-auth-manager node,
but this did not help either...
<security>
<anonymous-auth-manager/>
Kind Regards
-----Original Message-----
From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com]
Sent: 21 August 2012 23:04
To: users@qpid.apache.org
Subject: Re: java no-auth
The Java broker doesn't support Anonymous authentication in 0.16, but it does
as of 0.18 (which is currently being voted on for release, candidate artifacts
available at: http://people.apache.org/~jross/qpid-0.18/ ).
Support for Anonymous can be configured in etc/config.xml by replacing the
<pd-auth-manager> ... </pd-auth-manager> segment with
<anonymous-auth-manager/>. It is possible to have multiple auth managers with
per-port mappings but it doesn't sound like you need that functionality.
The QMF based python command line tools for the C++ broker have never been
particularly well supported by the Java broker, we have some unfinished
QMFv1 support in there but the substantially different QMFv2 came along shortly
after it was added and it sounds like the tools have finally moved to QMFv2 and
broken what functionality did work. We plan to extract the
QMFv1 support from the Java broker soon, until we can work on QMFv2 suport at a
later date. In the meantime the Java broker has a long standing JMX management
interface you can use with Jconsole/VisualVM/Qpid JMX Management Console/etc,
as well as a new HTTP management interface and web ui (replacing the JMX
console going forward) initially available in 0.18 and being improved beyond
that.
Robbie
On 21 August 2012 13:03, <laurent.deco...@sungard.com> wrote:
> Hello there,
>
> I would like to run the qpid-config python script against the java
> qpid-server.
>
> When I do something like
>
> python qpid-config add exchange topic MsgServer --durable --sequence
>
> I get
>
> Failed: AuthenticationFailure: sasl negotiation failed: no mechanism
> agreed
>
> If I was to run the Cpp version, qpidd with no-auth, that would work
> nicely.
>
> Now my question is: what do I need to configure to run my java server
> with the "no-auth" cpp equivalent ?
>
> Kind Regards
> Laurent
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
