[rabbitmq-discuss] Missing features making me look at moving off RabbitMQ

Christian Legnitto clegnitto at mozilla.com
Mon Nov 1 18:46:39 GMT 2010

Hmmm, I hadn't really thought of that, I'll look into it. You mean adding something like "secure.level.1" to the routing key and only letting certain users bind with with that? Is there a way to restrict bindings based on routing keys? Also, wouldn't # and * bypass that?


On Nov 1, 2010, at 8:38 AM, Scott Brooks wrote:

>> Support message-level permissions
>> * It'd be nice for a publisher to be able to include a security token and have the broker decide to vend to a consumer or not based on it
>> * Haven't really thought about this in-depth yet, but the problem we are trying to solve is publishing multiple-tiers of security-sensitive information where the message content itself determines who should see it
> Can you encode that security token into the binding on a topic
> exchange?  That would mean somewhat fixed values for your security
> token, and I can certainly see some ways that it wouldn't work, but
> you may be able to get things going.

More information about the rabbitmq-discuss mailing list