On November 18, 2026, between 13:00 and 16:00 CET, we will be replacing the identity and access management component responsible for signing you in and issuing the access tokens used by your applications. This maintenance will affect the EU environment only.
The new service uses the same endpoints and issues the same access tokens as the existing one, so for almost everyone there is nothing to prepare and nothing to change afterwards. There is one exception, and it concerns API clients that use the refresh_token grant — see Action Required below.
Action Required: API Clients Using Refresh Tokens
WARNING
If your integration uses the refresh_token grant, any refresh token obtained before the upgrade will stop working, and the token endpoint will return invalid_grant.
Your integration should recover on its own by starting a new authorization code flow, which is the standard response to invalid_grant. If your client does not handle this automatically, please re-authorize it once after the upgrade.
This is a one-time effect of the upgrade. Refresh tokens issued afterwards behave normally.
Client credentials integrations are unaffected and need no changes.
No Action Required
Everything you have configured on your side keeps working:
| What you use today | After the maintenance |
|---|---|
| All sign-in URLs — authorization, token, JWKS and discovery endpoints | Unchanged — same host names, same endpoint paths |
| Your credentials — user passwords and client secrets | Unchanged — no password reset, no new client secrets |
| Your OAuth2 clients | Unchanged — no client has to be registered again |
| Access tokens issued before the upgrade | Remain valid until their normal expiry. Running jobs and in-flight API calls are not interrupted |
| Token contents | Unchanged — no changes are needed in any service that validates our tokens |
| The identity providers your tenant signs in with, and your multi-factor authentication settings | Unchanged |
Rollouts that are already running and devices that are already downloading an update are not interrupted and continue as normal.
What You May Notice on November 18
You may be asked to sign in once more. If you are signed in to the web UI during the upgrade, you can keep working. The next time your session renews — within 2 hours — you may be returned to the sign-in page once. If your organisation signs in through a corporate identity provider, this will usually happen automatically, with no prompt.
As we transition to the new service during the maintenance window, you may also experience brief interruptions:
- Signing in to the console may temporarily fail and require a retry.
- Access token requests may fail or time out temporarily.
TIP
If one of your integrations treats a failed token request as a fatal error rather than retrying it, this is a good moment to check. A short retry with a backoff will carry it through the window without anyone noticing.
Why We Are Doing This
Today, managing access in Bosch IoT Rollouts means working across multiple places: users and roles in Rollouts, access rules for the Sign & Encrypt, and role mappings for the System Software Update. If you use more than one of these capabilities, you have to manage the same colleagues in multiple places, making it difficult to answer a seemingly simple question: "What can this person actually do?"
This maintenance is the first step towards bringing all access management into one place. Over the coming releases, this will deliver:
- One list of users and clients. Your users, API clients, and their assigned roles will be managed centrally and apply across Rollouts, Sign & Encrypt, and System Software Update.
- Access that reflects how your teams are organized. Permissions can be scoped to specific parts of your fleet, ensuring that each team can see and manage only the devices it is responsible for.
- One Access Management area in the console. No more separate access management pages for individual capabilities.
- More robust sign-in. Authentication will no longer depend on the availability of other parts of the platform.
We will keep you informed about each subsequent step and announce it here before it takes place.
Need Help?
If you have questions about this maintenance, please contact us at Bosch IoT Rollouts support.
