Closed AdamMiltonBarker closed 8 years ago
There is no relation, topic-based authorization is not supported at the moment, and I mean in general, not by this plugin.
Please ask questions on the mailing list.
On 20 abr 2016, at 5:26, AdamMiltonBarker notifications@github.com wrote:
Looks like your example just allows access if vhosts or resources or accessed (alos just found this in docs). I am just writing a php plugin for auth based on this plugin, In relation to MQTT topics can you explain the function of vhosts and resources.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub
OK so how do we authenticate a user to only subscribe to messages related to their account, thank you for the reply
Please post questions to rabbitmq-users or Stack Overflow. RabbitMQ uses GitHub issues for specific actionable items engineers can work on, not questions.
Like I said, there is no way to restrict access based on topics, see https://github.com/rabbitmq/rabbitmq-server/issues/505.
Thank you.
OK thanks
Looks like your example just allows access if vhosts or resources are accessed (after username / pass auth) (also just found this in docs). I am just writing a php plugin for auth based on this plugin, In comparison to MQTT topics can you explain the function of vhosts and resources.