You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requesting to have an authentication feature where someone can authenticate via HTTP POST requests, emqttd would make a request to the given http routes e.g /superuser, /acl, /userauth and on response code 200 the server would allow the client, or deny the client upon receiving other status codes e.g. 403.
This way anyone can implement their own authentication mechanisms e.g use of webtokens e.t.c through any language they prefer as a server running either locally or even on a different machine.
The text was updated successfully, but these errors were encountered:
Thanks for the new plugin! I'm lost on one point. How do I control whether the authentication request is for a superuser or a normal user? I'm connecting with a Node.js MQTT client, and I see that the first authentication attempt is a super_req, followed by an auth_req in case the super_req fails.
Requesting to have an authentication feature where someone can authenticate via HTTP POST requests, emqttd would make a request to the given http routes e.g /superuser, /acl, /userauth and on response code 200 the server would allow the client, or deny the client upon receiving other status codes e.g. 403.
This way anyone can implement their own authentication mechanisms e.g use of webtokens e.t.c through any language they prefer as a server running either locally or even on a different machine.
The text was updated successfully, but these errors were encountered: