Page History

...

This allows clients connecting using this username/password to subscribe on both the legacy Sparkplug STATE/PrimaryHostID, spBv1.0/STATE/PrimaryHostID , Sparkplug STATE and spBv1.0/GroupID# topics.

W device_one/temp/#, R state/#

This allows clients connecting using this username/password to publish on device_one/temp/# and subscribe on state/# legacy STATE topics

Examples For MQTT Engine ACLs

...

This allows Engine clients connecting using this username/password to subscribe and publish on the spBv1.0/STATE/PrimaryHostID Sparkplug STATE and spBv1.0/GroupID/+/EdgeNodeID/# topics

...

This allows clients connecting using this username/password to subscribe on both the legacy Sparkplug STATE and Sparkplug STATE topics and subscribe on the spBv1.0/GroupID/# topic

RW spBv1.0/STATE/PrimaryHostID, W spBv1.0/GroupID/NCMD/#, R spBv1.0/GroupID/#

This allows clients connecting using this username/password to subscribe on both the Sparkplug STATE /PrimaryHostID and spBv1.0/GroupID/# topics and subscribe publish on the spBv1.0/GroupID/NCMD/# topic.

Note

When creating an Access Control List (ACL) for an MQTT Engine client:

There must be RW privilege's for the MQTT Sparkplug™ B STATE message
- Sparkplug v3.0.0 state message topic: spBv1.0/STATE/primary_host_id
- Legacy Sparkplug state message topic: STATE/PrimaryHostID
- Review Changes to the STATE message in the Sparkplug v3.0.0 Specification for details on the legacy STATE client topic
There must be W privilege's for the Sparkplug NCMD message
- This by MQTT Engine to publish the Sparkplug Rebirth request
The MQTT Engine SparkplugB Namespace Filter must be configured for the same Group or Group/EdgeNode combination used in the ACL entry

...