You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the SDK does not validate the device ID and since it uses it to build the publish topic (instead of reading the certificate Common Name, like other SDKs) this could lead to devices being disconnected at the broker level (since they try to subscribe to topics for which they're not authorized).
The SDK should perform validation on the provided Device ID, and should possibly also use the Common Name of the certificate received from Pairing API as base for the device topic.
The text was updated successfully, but these errors were encountered:
Currently the SDK does not validate the device ID and since it uses it to build the publish topic (instead of reading the certificate Common Name, like other SDKs) this could lead to devices being disconnected at the broker level (since they try to subscribe to topics for which they're not authorized).
The SDK should perform validation on the provided Device ID, and should possibly also use the Common Name of the certificate received from Pairing API as base for the device topic.
The text was updated successfully, but these errors were encountered: