Option 1: Bosch IoT Rollouts Cloud User

• Rollouts Basic Auth as provided after booking
  User: "TENANT\USERNAME"
  Password: "PASSWORD"

Option 2: Authenticate with OAuth2

3rd party applications using or connecting to Bosch IoT Rollouts can also authenticate via OAuth2.

Two official grant types are currently supported, authorization code and client credentials. Please see RFC-6749 for detailed information.

Please note, that the tenant is always required as part of the URL, regardless of the grant type.

Certificate-based authentication

Bosch IoT Rollouts allows the authentication based on X.509 certificates. This is the preferred authentication mode. In this case, the target (device) needs to send a complete (self-contained) certificate chain along with the request which is then validated by a trusted reverse proxy. The certificate chain can contain multiple certificates, e.g. a target-specific client certificate, an intermediate certificate, and a root certificate.

After terminating the TLS connection, the proxy validates the certificate chain and, provided the chain is valid, retrieves the fingerprint of each certificate. The fingerprints as well as the common name of the client certificate are then forwarded to the DDI server using special HTTP headers. Note that the common name of the client certificate needs to match the ID of the addressed target. To establish trust with the client certificate of the target, the fingerprints of the root and intermediate certificate are then matched against the certificate fingerprints that are stored in the system configuration of your account.

If you want to use this authentication mode, you need to enable it for your account in the Configuration UI feature:

1. Enter edit mode via the Edit icon on the top right of the view.
   

   

2. Enable the Allow targets to authenticate via a certificate authenticated by a reverse proxy.

3. Аdd the certificate fingerprint of your intermediate or root CA.

Note: It is possible to enter multiple certificate fingerprints separated by semicolon. Bosch IoT Rollouts verifies that at least one of the provided fingerprints matches one of the incoming issuer hash headers. This is useful for certificate migration.

Find more details about this authentication mode including step-by-step instructions based on OpenSSL and cURL at Set up client certificate-based authentication for devices.

For a dedicated certificate management for embedded devices, please have a look at CycurV2X-PKI by ESCRYPT.

Target security token authentication

There is a 32 alphanumeric character security-token for each created target within Bosch IoT Rollouts. This token can be used to authenticate the target at Bosch IoT Rollouts through the HTTP-Authorization header with the custom scheme TargetToken.

The target security token is provided in Device Management Federation (DMF) API as part of the update message in order to allow DMF clients to leverage the feature or it can be manually retrieved per target by Management API or in the Management UI (Classic) in the target details.

Needs to be enabled for your account from the Configuration UI feature:

Gateway security token authentication

Often the targets are connected through a gateway which manages the targets directly and as a result are indirectly connected to the Bosch IoT Rollouts update server.

To authenticate this gateway and allow it to manage all target instances under its tenant there is a GatewayToken, to authenticate this gateway through the HTTP-Authorization header with a custom scheme GatewayToken. This is of course also handy during development or for testing purposes. However, we generally recommend to use this token with great care as it allows to act “in the name of” any device.

Needs to be enabled for your account from the Configuration UI:

1. Enable the Allow a gateway to authenticate and manage multiple targets through a gateway security token configuration.

2. Click Show and copy the token via the icon on its right.

Download artifacts

Within Bosch IoT Rollouts the artifact download is done by signed URLs. This means that there is no device authentication necessary (DDI credentials) when downloading an artifact. However, to get the download URL by deployment base the device has to be authenticated. Furthermore, the received download URL has a validity expiration of 1 month. This means that devices might have to re-call deployment base if access is denied. Artifacts are delivered through a worldwide Content Delivery Network (CDN) to provide high availability and performance for downloads.