I was able to set the sals mech using -Dqpid.sasl_mechs= or
sasl_mechs= in the connection URL
Ex.
"amqp://username:password@clientid/test?brokerlist='tcp://localhost:5672?sasl_mechs='ANONYMOUS''"
How did you set it ? using the JVM arg or the connection URL property?
Rajith
On Tue, Jul 19, 2011
It appears that the java client always wanted to connect PLAIN regardless of
the sasl_mechs settings to either PLAIN, ANONYMOUS or nothing at all. The
c++ update that I added from the repository appears to have added PLAIN on
the c++ broker side and that worked. I am using 0.10 java as well as
c++.
On 07/18/2011 10:16 PM, tnowicki wrote:
Using and setting sasl_mechs to ANONYMOUS did not seem to have any effect,
the c++ windows broker still reported PLAIN when I ran it with -t no matter
what.
Still did report PLAIN or did not? I thought the issue was that PLAIN
was not advertised and ther
Using and setting sasl_mechs to ANONYMOUS did not seem to have any effect,
the c++ windows broker still reported PLAIN when I ran it with -t no matter
what. With the addition of "PLAIN" in the cpp code (update to
SaslAuthenticator.cpp mentioned above) all worked fine even with no
sasl_mechs options
On 07/14/2011 11:10 PM, Steve Huston wrote:
I believe this is an issue with the Windows' C++ broker code that was
resolved recently by Gordon Sim. If you are up for checking the current
source code out from subversion, that should do it. Else I believe this will
be fixed in the 0.12 release comin
On 07/15/2011 03:28 AM, Rajith Attapattu wrote:
I believe the windows broker was defaulting to anonymous when
authentication was disabled and the JMS client didn't support it.
Since then we have added support for anonymous and this should work
fine with the upcomming 0.12 release.
The anonymous
I believe the windows broker was defaulting to anonymous when
authentication was disabled and the JMS client didn't support it.
Since then we have added support for anonymous and this should work
fine with the upcomming 0.12 release.
Rajith
On Thu, Jul 14, 2011 at 6:10 PM, Steve Huston wrote:
>
I believe this is an issue with the Windows' C++ broker code that was
resolved recently by Gordon Sim. If you are up for checking the current
source code out from subversion, that should do it. Else I believe this will
be fixed in the 0.12 release coming up within a few weeks or so.
-Steve
-O
