Overview of dynamic registration over HTTPS

Updated at:

The C Link SDK for IoT Platform provides a dynamic registration feature, also known as one-secret-per-product. This feature reduces provisioning costs because you do not need to provision each device with a unique device secret. Using the dynamic registration feature over HTTPS, a device can obtain the credentials required to connect to IoT Platform.

Prerequisites

Feature Description

An application calls the C Link SDK API to dynamically register a device over HTTPS and obtain the credentials required to connect to IoT Platform.

The following time series chart shows how an application implements this feature. The chart uses the ./demos/dynreg_basic_demo.c application as an example.

HTTPS dynamic registration process

For more information about the dynamic registration API over HTTPS, see aiot_dynreg_api.h.

Examples

  • For a code example of the dynamic registration feature over HTTPS, see Usage examples.

  • For descriptions of status codes related to the dynamic registration feature over HTTPS, see aiot_dynreg_api.h.

What to do next

After a device is dynamically registered, use the returned DeviceSecret, along with the ProductKey and DeviceName, to activate the device and connect it to IoT Platform. Depending on the protocol that your device uses, see the following topics:

Note
  • If a device is not activated, you can dynamically register it multiple times. The device uses the most recently received DeviceSecret. Ensure that the latest DeviceSecret is saved to the device.

  • If a device is already activated, you must call the ResetThing API operation to reset its dynamic registration status in the cloud. After the reset, you can dynamically register the device again.