We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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:
Is this need still relevant today? I would like to try to suggest an implementation for you.
Sorry, something went wrong.
No branches or pull requests
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: