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
how to set access control on a particular topic / client to prevent other clients from receiving sensitive messages, they can subscribe to wildcards to get all topic messages.
Maybe it's like socket.io which can create room and make clients join to certain rooms with unique keys so that other clients cannot easily listen.
Any best practice.
The text was updated successfully, but these errors were encountered:
https://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices/
Start from there. On aedes side there are authenticate and authorize functions that could help in this. Best practice in general from what you are looking for is to embed an id to topics and use aedes aithorize functions to enable some clients to subscribe/publish to certain topics
On 24 Jun 2020, at 18:58, Imanuel Pundoko ***@***.***> wrote:
hello, I just know mqtt
how to set access control on a particular topic / client to prevent other clients from receiving sensitive messages, they can subscribe to wildcards to get all topic messages.
Maybe it's like socket.io which can create room and make clients join to certain rooms with unique keys so that other clients cannot easily listen.
Any best practice.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
@robertsLando thank you for fast respond. It can be done with authorize function, with compare stored authenticated client and i can revoke client who trying to subscribe to specific topic.
Now my problem solved. Thanks.
hello, I just know mqtt
how to set access control on a particular topic / client to prevent other clients from receiving sensitive messages, they can subscribe to wildcards to get all topic messages.
Maybe it's like socket.io which can create room and make clients join to certain rooms with unique keys so that other clients cannot easily listen.
Any best practice.
The text was updated successfully, but these errors were encountered: