<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Prevent access to my IoT&#x27;s]]></title><description><![CDATA[<p dir="auto">Now my question is whether it is possible to prevent<br />
access to my IoT's from a cell phone (App Gui-O) of some employee who is no longer working in the company, without having to change the firmware of all the IoT's.</p>
<p dir="auto">This is a question that certainly some customer in the future will ask</p>
<p dir="auto">Regards</p>
]]></description><link>https://forum.gui-o.com/topic/34/prevent-access-to-my-iot-s</link><generator>RSS for Node</generator><lastBuildDate>Sun, 10 May 2026 23:12:58 GMT</lastBuildDate><atom:link href="https://forum.gui-o.com/topic/34.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 18 Jan 2022 21:36:26 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Prevent access to my IoT&#x27;s on Wed, 19 Jan 2022 11:16:32 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.gui-o.com/uid/4">@kl3m3n</a></p>
<p dir="auto">Thank you for the explanation</p>
<p dir="auto">Best regards</p>
]]></description><link>https://forum.gui-o.com/post/46</link><guid isPermaLink="true">https://forum.gui-o.com/post/46</guid><dc:creator><![CDATA[Sato]]></dc:creator><pubDate>Wed, 19 Jan 2022 11:16:32 GMT</pubDate></item><item><title><![CDATA[Reply to Prevent access to my IoT&#x27;s on Wed, 19 Jan 2022 10:56:59 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.gui-o.com/uid/8">@sato</a> said in <a href="/post/44">Prevent access to my IoT's</a>:</p>
<blockquote>
<p dir="auto">Now my question is whether it is possible to prevent<br />
access to my IoT's from a cell phone (App Gui-O) of some employee who is no longer working in the company, without having to change the firmware of all the IoT's.</p>
<p dir="auto">This is a question that certainly some customer in the future will ask</p>
<p dir="auto">Regards</p>
</blockquote>
<p dir="auto">Hello,</p>
<p dir="auto">you have several options to implement <strong>authentication</strong> and <strong>authorization</strong>.</p>
<p dir="auto">MQTT by design allows specifying <strong>user</strong>, <strong>password</strong> and <strong>client id</strong> parameters. Based on this credentials, the broker can then decide if a client connection is allowed (in theory, you could also use client certificates, but GUI-O currently does not support importing custom certificates). You could for example only check the <strong>client id</strong> and disable <strong>user-password</strong> authentication (depends on your use case).</p>
<p dir="auto">The main "problem" is that this access control requires broker access to setup the rules properly. Although we offer MQTT broker functionality out of the box, we currently do not offer users to setup custom rules (like CloudMQTT or HiveMQ does).</p>
<p dir="auto">When the rules are set, you can simply remove the client by updating the rules. Furthermore, you can also allow a certain client to access a device (topic), while denying access to other clients.</p>
<p dir="auto">I hope I was clear.</p>
<p dir="auto">Best regards,<br />
kl3m3n</p>
]]></description><link>https://forum.gui-o.com/post/45</link><guid isPermaLink="true">https://forum.gui-o.com/post/45</guid><dc:creator><![CDATA[kl3m3n]]></dc:creator><pubDate>Wed, 19 Jan 2022 10:56:59 GMT</pubDate></item></channel></rss>