Credentials Secret, Pairing and Transports
Once a Device has performed its first registration through an Agent, it holds its Credentials Secret. This Credentials Secret is the token the device uses for performing the actual Pairing routine, which results in the device obtaining its Credentials for accessing its designated Transport.
A Device's Credentials Secret allows access to Pairing API's Device REST API, which is then used for obtaining information about which Transports the Device can use for communicating, and for obtaining Credentials for its assigned Transports.
The ability to request Credentials of a Device can be inhibited with AppEngine
API or using
astartectl with this command:
astartectl appengine devices credentials inhibit <device_id_or_alias> true \
-k <appengine-key> -r <realm-name> -u <astarte-api-url>
Once its credentials_inhibited field is set to true, a Device is not able to request new
Credentials. Note that Credentials that were already emitted will still be valid until their
expiration.
As, from a user's standpoint, the way a Device communicates with Data Orchestrator is entirely Transport-specific, this guide will cover using Data Orchestrator/MQTT through one of Data Orchestrator's SDKs. If you are using a different Transport, please refer to its User Guide, or if you wish to implement your own, head over to Transport Developer Documentation.