[rabbitmq-discuss] Access Control required for RabbitMQ and Management plugin

Saurabh Sharma saurabh.infoedge at gmail.com
Fri Dec 20 16:38:44 GMT 2013


Hi Simon ,
Thanks for your reply..

I am using three users
//for monitoring purpose
permission "alivenss-test.*" "" ".*"

//for read write
permission "" ".*" ".*" (instead of making "amq\.default" , i am keeping
configure as " " and it is working)

do "" means "^$" or "amq\.default" ?

//for all three
permission ".*" ".*" ".*"



Thanks
Saurabh





On Fri, Dec 20, 2013 at 6:03 PM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 20/12/13 06:43, Saurabh Sharma wrote:
>
>> 1) i want to create a user who can make call to api for aliveness test
>> and querying queues.
>> i am setting permission like
>>
>> rabbitmqctl set_permissions -p / monitor "^(.\.aliveness-test.*)$"
>> "^(.\.aliveness-test.*)$" ".*"
>>
>> but still getting the error that
>> "error":"not_authorised","reason":"ACCESS_REFUSED - access to queue
>> 'aliveness-test' in vhost '/' refused for user 'monitor'"
>>
>
> Those brackets and dots are not needed. Also the aliveness-test publishes
> to the queue via the default exchange, so you need to define permissions
> for that. So:
>
> $ rabbitmqctl set_permissions -p / monitor "^aliveness-test$"
> "^amq.default$" ".*"
>
> should work.
>
> Cheers, Simon
>
>
> --
> Simon MacMullen
> RabbitMQ, Pivotal
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131220/ee0acb6b/attachment.html>


More information about the rabbitmq-discuss mailing list