Versions Compared

Old Version 31

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version 32

changes.mady.by.user Gill Houghton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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


Note

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

  • There must be R privilege's for the Sparkplug NCMD message
    • This is used by MQTT Transmission to subscribe to the Sparkplug Rebirth request
  • There must be R privilege's for the Sparkplug NDEATH message
    • This is used by MQTT Transmission to subscribe to its own STATE message

Examples For MQTT Engine ACLs

...

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
  • There must be W privilege's for the Sparkplug NCMD message
    • This is used 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

Client Connection Issues

If MQTT Engine or MQTT Transmission client attempts to subscribe on a topic that is not allowed by the ACL for that client, the connection will fail and the client will not attempt to reconnect.

For example with R spBv1.0/My MQTT Group/NDEATH/PLC 1, W # the Transmission client is not able to subscribe to the NCMD and DCMD topics

Image Added


If MQTT Engine or MQTT Transmission client attempts to publish on a topic that is not allowed by the ACL for that client, the connection will be forcefully closed and the client will attempt to reconnect.

For example with R #, W spBv1.0/My MQTT Group/+/PLC 1 we are able to publish the NBIRTH for PLC 1 but are not able to publish the DBIRTH for D1

Image Added



Additional Resources

...