[rabbitmq-discuss] shovel auth change in 3.3.0?

Simon MacMullen simon at rabbitmq.com
Fri Apr 4 11:31:22 BST 2014

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

More information about the rabbitmq-discuss mailing list