In the second half of 2024, the Bosch IoT Rollouts authentication host was changed from access.bosch-iot-suite.com to access.eu1.bosch-iot-rollouts.com, with /token being replaced by /oauth2/token and the /v2 prefix removed from all other endpoint paths.
Does This Affect You?
Only if any components in your environment still use the old hostname (access.bosch-iot-suite.com) or its associated endpoint paths (/token and /v2 prefix)
If you are not sure, the check takes a minute: search your configuration for the old hostname and the old paths, as described under What Do You Need to Do? below.
Why We Are Sending This Reminder
This is a reminder of a change announced in the second half of 2024. Nothing about it is new.
We have extended the deadline to March 1, 2027, giving everyone more time to plan and complete the migration. This also provides an opportunity for those who may have missed our original announcement in 2024 to catch up and transition at their own pace.
What Changed?
Two things changed: the host name, and the path of every endpoint you call.
Host name
| Host name | |
|---|---|
| Migrate from | access.bosch-iot-suite.com |
| Migrate to | access.eu1.bosch-iot-rollouts.com |
Endpoint paths
| Old path | New path | |
|---|---|---|
| Token request | /token | /oauth2/token |
| All other endpoints | /v2/<path> | /<path> |
IMPORTANT
Changing the host name alone is not enough. A client that points at access.eu1.bosch-iot-rollouts.com but keeps its old paths will not work. Update both.
Timeline
| Date | Change |
|---|---|
| Now | - The access.eu1.bosch-iot-rollouts.com hostname and its endpoint paths are available and ready to use.- The old hostname access.bosch-iot-suite.com and its endpoint paths are still supported, so clients using them keep working.- Please complete the migration at your earliest convenience, and no later than March 1, 2027. |
| March 1, 2027 | The old hostname access.bosch-iot-suite.com and its endpoint paths will be decommissioned, and all requests to them will fail. |
WARNING
There will be no further extension. Plan your migration so that it is finished well before March 1, 2027.
What Do You Need to Do?
- Search for three strings —
access.bosch-iot-suite.com,/tokenand/v2/— across your applications, device integrations, CI/CD pipelines, scripts, configuration files and stored secrets. If none of them appears, you are done. - Update every hit to the new hostname and path shown under What Changed?. A client already on the new hostname may still call the old paths, so check the paths even where the hostname is correct.
- Open the new hostname in your network before you switch over. If your clients pin certificates, or your firewall allows outbound traffic only to named hosts or fixed IP addresses, add
access.eu1.bosch-iot-rollouts.comthere. - Test one client end to end. It should obtain an access token from
access.eu1.bosch-iot-rollouts.com/oauth2/token, and its subsequent API calls should succeed. - Roll out to your fleet, then run the search from step 1 again to confirm nothing is left behind.
Need Help?
If you are unsure whether you are affected, or need assistance with the migration, please contact us at Bosch IoT Rollouts support.
