[rabbitmq-discuss] Problems with STOMP & access control

[Lionel Cons]

I've read http://www.rabbitmq.com/access-control.html and
http://www.rabbitmq.com/stomp.html and I did not find any practical
way to use access control with STOMP.

In the STOMP world (in fact, since STOMP is broker behavior agnostic,
this is rather tied to the JMS world), one can use destinations like
/queue/test.foo or /topic/test.bar. It would be natural to use these
names in the access control regexps to allow, for instance, a given
user to access all queues matching "test\..*".

Unfortunately, the STOMP destinations names get mapped to AMQP
resource names that loose the original names, for instance
amq.gen-AXVr2gFuBTO4duQ5OEC9b9.

Is there a way in RabbitMQ to use access control based on the STOMP
destination names?

Cheers,

Lionel