[rabbitmq-discuss] shovel auth change in 3.3.0?
michael.laing at nytimes.com
Fri Apr 4 12:52:34 BST 2014
Thanks I'll try to make a test case - I've already added passwords to our
dev environment so all works as it did before now. It was an auth error.
As I was updating them, I noticed that, although the passwords had been
left out, the colon was still there, so it may have been a parsing
difference. Of course the colon shouldn't have been there.
On Fri, Apr 4, 2014 at 6:31 AM, Simon MacMullen <simon at rabbitmq.com> wrote:
> On 03/04/14 18:30, Laing, Michael wrote:
>> It appears that either the the source brokers or the destination brokers
>> must now have a password provided even when using direct connection to
>> both vhosts, i.e. the shovel is connecting vhosts on the same cluster.
>> Formerly no password was required for either.
> That really should not be happening - and in fact I just tested it and I
> could still set up a shovel specifying username but no password over a
> direct connection.
> Furthermore, in 3.3.0 if you specify no username for a direct connection
> it should always work rather than requiring the guest user to exist.
> So I'm curious: how exactly are you doing this? What error do you see?
> Cheers, Simon
> Simon MacMullen
> RabbitMQ, Pivotal
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss