MQTT Security LTE-M
-
I am having a problem figuring out how to secure my mqtt connections. I want my devices to publish to their own uplink topic and check their downlink topic when we want to push some configuration. I am using sims from 1nce with a 500MB limit so stuff needs to be lightweight and RabittMQ + mqtt seems to fit the bill.
Using TLS and user/password is fine but I would like to isolate each device and maintaining a Access Control List on my broker with unique user/pass for each device seems like an error prone and cumbersome solution. Using the same username/pass for all the devices is just a horrible idea for security and traceability.
Been trying to figure out OAuth 2.0 + mqtt but not really finding any good resources.
Had a look at Hashicorp Vault that exposes a nice API to dynamically creating user/pass on rabittmq that looks nice with regards to not spreading secrets to all the devices, tracebility and revoking access if a device is compromised, but I can not figure out how to use Vault with my pycom devices.
1nce has a SIM-as-an-Identity thingy that looks pretty interesting but it looks like it depends on AWS-Iot-Core that I would like to avoid using. Is it possible to use SIM-as-an-Identity to authorize devices to topics without AWS-Iot-Core.
This seems like such a common use case but I am really struggling to find a good solution, any suggestions are much appreatiated.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login