-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for HTTP Authentication Backend #246
Comments
Is this need still relevant today? |
It's pretty much mandatory for us... we need an external mechanism to authenticate users. |
@JadeKharats Hi :) a contribution would be very appreciated, feel free to fork and make a PR if you have something in mind! |
I was thinking of redefining UserStore as an abstract class. I'll try to do that this weekend, if the solution works for you. P.S.: I'll also add cache management and a validity period in the config. |
speaking as a user, that makes perfect sense to me. I was just getting familiar with the code (and the language). Your timing is perfect for us. |
Hi, I would like to add in the Today the You prefer that I put my code directly in the spec_helper or that I externalize it |
I should add the backend parameters in the config. |
Main for sure, it applies to all interfaces, mgmt, amqp and mqtt |
Make sure that multiple backends can be used at the same time. You can have some admin user in the built in user store and the rest in the http backend for instance. |
Or make a new section called [auth] |
@JadeKharats I opened a draft PR that might cross over what you are doing, feel free to add comments there with any findings/input you have gained while looking at this. |
In combination with Websockets it makes sense to delegate authentication to a http backend.
Can look at https://github.com/rabbitmq/rabbitmq-server/tree/master/deps/rabbitmq_auth_backend_http for inspiration.
Probably integrate caching by default, as every user action, including publishes requires an authentication lookup.
The text was updated successfully, but these errors were encountered: