-
Notifications
You must be signed in to change notification settings - Fork 47
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
401 status still let the client to pub/sub #48
Comments
is this fix? as I am getting the same issue for v3. |
@zsafder Have you turned off anonymous access in |
yes, allow_anonymous is false. Below is my docker run command. Kindly let me know what I am missing here.
|
@tigercl waiting for your help, I am stuck there. |
Hi @zsafder can you give me the precise version used? Is it v3.2.3? |
I have same problem! Actually I checked also the logs from my http server and it never calls the ACL ap i! |
@tigercl it is 3.2.7 |
What I have observed now, the client can able to publish a message and subscribe call return true by EMQX cluster but there is no topic created in the case of a 403 response. The solution we would like to achieve is the client should not able to publish/subscribe to the cluster. |
Ideally, I would like to send 403 code to client pub/sub requests. Can I do that? Or denial will be silent to clients? Currently, clients cannot able to do pub/sub but they are getting 200 response. |
Yes, you can. The emqx-auth-http/src/emqx_acl_http.erl Lines 57 to 65 in 20660de
|
In v2.3 for ACL, I am returning 401.but the client is still able to pub/sub.
The text was updated successfully, but these errors were encountered: