Self-registration of devices

Devices can register themselves via the Device API in the Device Portal.

All self-registration information can be found in the Device API description.

To use self-registration, devices must be able to authenticate themselves in the Device Portal using certificates.

All information for implementing device authentication is located here: Implementing certificate authentication

Establishing Communication Between the Device and the Device Portal

Once the devices have been registered in the Device Portal, communication can be established. All relevant end points for communication are stored in the Device API.

In addition to selecting the correct endpoint, the device must authenticate itself in the Device Portal. Two methods are available in the Device Portal for authenticating device communication:

Basic Auth (recommended for test devices only)
Registration is done by simple authentication by user name and password.

A user name and password for the device are currently provided via the Helpdesk
Certificate authentication
Devices are authenticated by means of certificate X.509, which must first be set to the whitelist in the Device Portal.

To use certificate authentication, the devices must be switched from test to productive operation: Switching Devices from Test to Productive

Once Basic Auth communication has been implemented, a device is always uniquely identified by the Communication ID.

When using the Device Portal Cloud solution, the Helpdesk will indicate a corresponding Communication ID area for quality assurance.

Using the Communication ID provided and API documentation, it is possible to update the status information for the devices. For the first tests, it is recommended to use the Swagger UI and any tool for HTTPS requests, such as Postman.