All,
I had the opportunity to review the MQTT-TLS profile for ACE [1] and
I’d like to share my thoughts with this list.
The document at hand proposed that token expiry checks take place on
PUBLISH, SUBSCRIBE or CONNECT actions. I’d like to note that it might
be worthwhile to have the token expiry checks for PINGREQ packets in
order to make sure that “sleeping” MQTT clients which do not send
PUBLISH or SUBSCRIBE packets can get disconnected at the next possible
client interaction with the broker.
On a sidenote: In a recent MQTT project with millions of constrained and
untrusted devices (connected via unreliable communication channels), an
almost identical approach as proposed in the draft was implemented. The
authentication and authorization was implemented exactly as described in
this document with the use of the Introspection API and “offline
validation” of JWTs. So I can confirm that the approach proposed is
actually usable at scale and works very well with some existing MQTT
brokers.
All the best,
Dominik
[1] https://www.ietf.org/id/draft-sengul-ace-mqtt-tls-profile-01.txt
_______________________________________________
Ace mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ace
