[rabbitmq-discuss] MQTT topic ACLs Query

[Mark Wolfe]

Cheers for the update, I look forward to hearing what ideas come out of it.

In the short term it looks like I am going to have to build an adapter to
solve the problem I currently have, probably in a similar vein to the
current MQTT plugin.

As my requirements are very simple I will probably just partition the
topics for each gateway device.

The basic ideas is to authenticate each gateway device using a
username/pass and once connected add a configurable prefix to the routing
keys using the same pattern as is currently used. this will effectively
partition the topic tree for each gateway. Note the value of the prefix
attribute will be loaded from LDAP and will not be exposed to the gateway.

Just to complete the picture I have a router of sorts on AMQP side which
dispatches these messages to existing application code which interacts
either with the database or forwards it onto some other AMQP driven
services which interface with third parties via REST.

This won't affect MQTT but will influence how the data is bridged into
AMQP, giving me what i am after which is a level of isolation for outside
gateway devices, while retaining the simple internal structure you have now.

If anyone has any other suggestions or questions I am all ears.



On Fri, Jan 10, 2014 at 7:32 PM, Emile Joubert <emile at rabbitmq.com> wrote:

>
> Hi Mark,
>
> On 07/01/14 12:10, Mark Wolfe wrote:
>
> > Hopefully that gives you some insight into what I am hoping to achieve.
>
> It does, thanks for the detail. I have filed a ticket to assess the
> feasibility of implementing this feature, preferably in a way that is
> compatible with the other protocols implemented by RabbitMQ.
>
>
>
> -Emile
>



-- 
Regards,

Mark Wolfe

--
I am not young enough to know everything.
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140112/0f7cdb8a/attachment.html>