You need to use `rabbitmqctl set_permissions` to grant UserB full permissions on QueueB
and no most only write (configure allows for deletion, read allows for consumption) permissions on QueueA.
If I were you I'd restrict UserB from doing anything with QueueA and then see if you actually need
to grant write permissions for anything.
A wiser idea to not fixate on just one queue but rather fix a queue name prefix for each user,
e.g. instead of
rabbitmqctl set_permissions -p / user_b "queue_b" "queue_b" "queue_b"
do something like
rabbitmqctl set_permissions -p / user_b "group_b\.*" "group_b\.*" "group_b\.*"
and name your UserB queue(s) "group_b.something-meaningful", "group_b.something-else" and so on.
Since you won't be modifying the administrative's user permissions, I cannot think of
a way that can affect QueueA operations.
> --
> You received this message because you are subscribed to the Google Groups "rabbitmq-users"
> group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
rabbitmq-user...@googlegroups.com.
> To post to this group, send an email to
rabbitm...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.
>
--
MK
Staff Software Engineer, Pivotal/RabbitMQ