Replies: 1 comment
-
looks like a typo. You have an identical URL for all three endpoints. Start with verifying effective configuration and consider using the "new" (has been around for a few years now) configuration format which the HTTP authN backend supports: auth_backends.1 = http
auth_http.http_method = post
auth_http.user_path = http://some-server/auth/user
auth_http.vhost_path = http://some-server/auth/vhost
auth_http.resource_path = http://some-server/auth/resource
auth_http.topic_path = http://some-server/auth/topic |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi expert,
Would you help on one questions? Very appreciated for your response.
1. I enabled the plugin rabbitmq_auth_backend_http to verify the client, following is my configuration:
[
{rabbit, [{auth_backends, [rabbit_auth_backend_http]}]},
{rabbitmq_auth_backend_http,
[{http_method, post},
{user_path, "http://host.docker.internal:3001/users"},
{vhost_path, "http://host.docker.internal:3001/users"},
{resource_path, "http://host.docker.internal:3001/users"},
{topic_path, "http://host.docker.internal:3001/users"}]}
].
2. And i set the user name and password with connect option:
3. But I could not get the username and password from body, the body is empty:
Beta Was this translation helpful? Give feedback.
All reactions