[rabbitmq-discuss] Permission handling changed on 2.2.0?
alexandru at rabbitmq.com
Thu Dec 2 09:52:48 GMT 2010
We changed the way permissions work in 2.1.0 and 2.2.0.
In previous releases, every client would implicitly have access to
server-generated names (amq\.gen.*). This is no longer the case.
The current permissions mechanism is described in our administration
You probably want your individual permissions to be
'^amq\.gen.*|ping$' and not just ping.
On Thu, Dec 02, 2010 at 01:08:55AM -0800, Ivan Sanchez wrote:
> Hi all,
> I've upgraded to 2.2.0 and since then I can't get my consumers to
> work with our previous permissions. For instance, if I have
> permissions like:
> rabbitmqctl set_permissions ping ping ping ping
> Then I get the following error:
> connection <0.4248.0> (running), channel 1 - error:
> "access to queue 'amq.gen-STvK+LmDNxQrlLAUaVNfSg==' in
> vhost '/' refused for user 'ping'",
> The consumer code has not been changed, and it never had to define
> queue names before. Reading the docs it seems like that was wrong, but
> since we never had permission problems now I'm confused.
> Am I missing something?
> Thank you for your help,
> Ivan Sanchez
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss