In case you need to configure a cloud-to-cloud integration to transfer your IoT data, you can define a main IoT Connector, that is automatically used by all DPS's registered things.
For security reasons, the main IoT Connector should be used only for cloud-to-cloud communication, and not for thing-to-cloud communication. It is strongly discouraged to store in each client (e.g. thing) or let each client directly access the main IoT Connector configuration (e.g. credentials, certificates, endpoints).
It is enough for one client to be hacked to allow the hacker to read data from all clients or, even worse, to send malicious messages (e.g. commands) to other connected clients.
The main configuration of the IoT Connector must be kept secret from the single cloud client.
Configuring the main IoT Connector
In order to configure a main IoT Connector, you should:
- Enter the Integrations / IoT Connector page.
- Select the IoT Connector from the enabled ones.
- Provide the required properties to configure the connection (e.g. credentials, certificates, endpoints).
By default, you can leverage the STC connector, but optionally you can enable others within the Integrations / Plugins page.
When done, on each Thing, you will see that the main connector is used, and only a few properties can be configured (e.g. Asset Id, Path).
Optionally, the main connector can be overwritten, punctually redefining all properties of the connection.
When a Thing inherits the main IoT connector, the connection properties (e.g. credentials) are obfuscated for security reasons (see security warning above). The same is valid for location and customer mapping.
Note that, via API, there is no way to obtain the full configuration of the main IoT Connector.