[rabbitmq-discuss] User Access Control

[Michael Teo]

Hi, Ben.
Thanks for the link to the post. I didn't realize that realms were going
to be deprecated soon.

Am I correct to say that when the realms have been dropped, RabbitMQ
server implementation will not have any measures to limit the clients to
be able to subscribe/publish to certain queues or exchanges ?

Michael


Ben Hood wrote:
> Michael,
> 
> On Sat, Sep 27, 2008 at 7:55 AM, Michael Teo <rabbitmq.com at miketeo.net> wrote:
>> Hi, I have just started using Stomp with RabbitMQ, and would like to
>> clarify if I can limit user access to queues or exchanges.
>>
>> My scenario as follows:
>>
>> Stomp Publisher: publish updates to /channels/#
>> Stomp Consumer A: subscribes and receives updates from /channels/A
>> Stomp Consumer B: subscribes and receives updates from /channels/B
>>
>> Is there any settings/configurations which I can use to prevent Consumer
>> A from subscribing to /channels/B or even /channels/# ?
>>
>> I have read up Administration Guide and understood that there are realms
>>  and permission flags like passive, active, write, read or all, but I
>> can't seem to relate the concepts of realms with queues in the RabbitMQ.
> 
> There was a thread about this on the list recently:
> 
> http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2008-September/001896.html
> 
> HTH,
> 
> Ben
>