Bosch IoT Device Management - will be discontinued by mid 2024

Manage credentials

A device in Bosch IoT Hub can have multiple credentials associated with it. They act as a proof of identity with the IoT Hub during the connection establishment.


Your are logged in to the Bosch IoT Hub - Management API. Refer to Login to Bosch IoT Hub - Management API.

Add device credentials

Credentials are required to authenticate your device with the IoT Hub. Credentials can also be managed with the Management API. Adding device credentials is done by performing a HTTP POST request which contains the credentials information.

For security reasons credentials are stored in IoT Hub in hashed format, as defined with the type field ("type": "hashed-password", see examples below).

  1. In the Management API navigate to the credentials section and select the POST operation.

  2. Press the Try it out button.

  3. Enter your tenant-id in the tenant-id field.

  4. Adapt the device-id field of the request to match the device created in the previous step.

  5. For password credentials, the auth-id property will be the username that will be used to authenticate for device connectivity.

  6. To create a password secret, which will be used by a device to authenticate itself with the Bosch IoT Hub, please create a strong password (e.g. at least 8 characters combining letters, numbers and special characters).
    Please note that you will need the password you have created later on, for example for authenticating your device in order to send messages to IoT Hub.
    For the security reasons the IoT Hub only stores passwords in a hashed format internally. Provide the plaintext password string in the password field. Bosch IoT Hub will add salt and hash it.

  7. Verify that the request was successful (Code 201).

Please take into account that the protocol adapters of the Bosch IoT Hub have a caching mechanism in place for devices and their credentials. That means if you make changes in the device’s or credentials' properties, it takes some time until the protocol adapters apply the changes. Currently the cache setting is configured to 10 minutes.