Closed farahamawi closed 6 years ago
Thank you for your time.
Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. GitHub issues are not used for questions, investigations, root cause analysis, discussions of potential issues, etc (as defined by this team).
We get at least a dozen of questions through various venues every single day, often light on details. At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because GitHub is a tool our team uses heavily nearly every day, the signal/noise ratio of issues is something we care about a lot.
Please post this to rabbitmq-users.
Thank you.
See the resource_path endpoint and Access Control doc guide. Several example implementations are also available.
I started using this plugin, I added a path(endpoint) for user login to rabbitmq, However I need to authorize users (admin user / readonly user) sending user tags along with the response is not enough.
I tried to send http request from my server to rabbitmq to configure user permissions
/api/permissions/${vhost}/${username}
before send 'allow' to the broker. is there another way to send the permissions with the response?