Topic authorization

[V Z]

Mosquitto and IBM MessageSight implement this nifty scheme to control who can subscribe and publish to which topics. First, we can specify allowable topic strings and patterns like animals/dogs, animals/cats, animals/#, animals/fourlegged/#, etc. Second, we can use substitutions to reflect client id and authenticated use id (%c and %u respectively in Mosquitto), e.g. we can limit the user to subscribe only to "own" topics like stuff/%u/# .

Both are very similar, but I don't believe are part of MQTT spec. Is this a de-facto standard or is there work to standardize this at OASIS?

[Paul Fremantle]

There is no work that I know of to standardize this. 

Paul

On 9 September 2016 at 20:24, V Z <uvzu...@gmail.com> wrote:

Mosquitto and IBM MessageSight implement this nifty scheme to control who can subscribe and publish to which topics. First, we can specify allowable topic strings and patterns like animals/dogs, animals/cats, animals/#, animals/fourlegged/#, etc. Second, we can use substitutions to reflect client id and authenticated use id (%c and %u respectively in Mosquitto), e.g. we can limit the user to subscribe only to "own" topics like stuff/%u/# .

Both are very similar, but I don't believe are part of MQTT spec. Is this a de-facto standard or is there work to standardize this at OASIS?

--
To learn more about MQTT please visit http://mqtt.org
---
You received this message because you are subscribed to the Google Groups "MQTT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mqtt+unsubscribe@googlegroups.com.
To post to this group, send email to mq...@googlegroups.com.
Visit this group at https://groups.google.com/group/mqtt.
For more options, visit https://groups.google.com/d/optout.

--

Paul Fremantle

Part-time PhD student - School of Computing

email: paul.fr...@port.ac.uk, pa...@fremantle.org

twitter: pzfreo / skype: paulfremantle / blog: http://pzf.fremantle.org

Co-Founder, WSO2
Apache Member and Committer
07740 199 729

[V Z]

Thanks. Do you think that approach is worthy of standardization, maybe as an add-on profile, or is there a better one?