User permission to only access specific queues in a topic. #7944
-
|
To set topic permissions, you must use What do the regexes match? Does it match the queue name or routing key? We plan to create users who can only publish and read on specific queues (MQTT). Is that possible with this endpoint? Or is it possible at all? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Beta Was this translation helpful? Give feedback.
-
|
All MQTT clients publish to the same topic exchange ( The queues used by the MQTT plugin are named using a convention, More importantly, topic permissions include variable expansion and |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for answering my question! |
Beta Was this translation helpful? Give feedback.
All MQTT clients publish to the same topic exchange (
amq.topicby default but can be overridden).Topic permissions exist exactly for the needs of MQTT and STOMP users.
The queues used by the MQTT plugin are named using a convention,
mqtt-*, which allows you to limit access to them for a specific user or set of RabbitMQ users.More importantly, topic permissions include variable expansion and
client_idis one of the expanded variables, which can help limit access of specific MQTT clients to just their topics.