Dynamic Proxying of MQTT based on client auth.

[nzfarmer1]

Here is a challenge that's been troubling me for sometime.

Let's say we have multiple mqtt clients and multiple mqtt backends BUT only one public facing server/port.

We want to identify a user via say their client's SSL Cert or username/password, then proxy all requests for that Client Id (source port/address) to a specific broker based on a lookup table.

Would we be able to configure your tool to support this requirement?

Thank you.

[njh]

Hello,

It isn't far off but the following limitations probably make it worth looking at something else:

• The proxy class doesn't support SSL
• The proxy is only currently able to talk to a single backend
• The ruby implementation won't be that performant compared to other implementations

Node.js might be a better choice for this type of thing.

nick.

[nzfarmer1]

Thanks nick

You inspired me to roll this today: https://github.com/nzfarmer1/mqtt-proxy

andrew

[njh]

Great!