Registration options for the tutorial

Tip: If you cannot access some of the repositories referenced in this section, please contact us to request access.

Device Management offers two modes to register devices - Bootstrap and LwM2M. The Device Management Client Example supports both, and can also support using your own certificate:

• Bootstrap with Device Management-provided certificates (developer mode): This is the default mode, and the steps to perform it are listed in the example documentation.

• Bootstrap with your own certificate: This is an advanced option, and is not documented with the example. If you want to use it:

  • Inject credentials to your device using the factory client example.
  • The client requires certain parameters in a specific format, as detailed in the Provisioning guide.
  • You will need to disable the developer mode for the example application if you want to use this method, as explained below.

• LwM2M with your own certificate authority: This is an advanced option, and is not documented with the example. If you want to use it:

  • Inject credentials to your device using the factory client example.
  • The client requires certain parameters in a specific format, as detailed in the Provisioning guide. If parameters are missing or not formatted correctly, your client will not connect to Device Management; it will return the error MbedCloudClient::ConnectInvalidParameters.
  • You will need to disable the developer mode for the example application if you want to use this method, as explained below.

Disabling developer mode

If you want to use one of the advanced registration options, you must disable the bootstrap-developer mode that the example uses by default.

Mbed OS

Open the mbed_app.json file, and change the value of developer-mode from 1 to null:

"developer-mode": {
"help": "Enable Developer mode to skip Factory enrollment",
"value": null
}

Linux

Open the CMakeLists.txt, and remove add_definitions(-DMBED_CONF_APP_DEVELOPER_MODE).