Overview

Switch is in the process of changing its current IAM to Auth0. This change will require integrators to make small changes to their integration specifically how the access token is fetched from the IAM and the details when doing this, such as the token URL, client ID, client secret etc.

Beside the changes of the applications that integrated with the Switch APIs, part of the users will be impacted as well as explained further down.

The migration to Auth0 will go into 2 phases where first the test environment will be migrated and some period after this, not defined yet but aproximatly 1 month after test environment is migrated, the production environment will be migrated as well. We will post more detailed timeplan as soon as we have agreed on it.

Changes

The following are the changes will impact both the users that log into the Switch portal and the applications that connect to the Switch APIs:

Users

• Users that log into the Switch platform using username and password will be required to use the "Forgot password" functionality on the login page to reset their password. At the same time, on the first login the user will be required to set MFA.

• Users who are federated and use their company accounts to login to the Switch platform do not require any action and the linking of their company accounts with their Switch account will happen automatically.

Organization clients

• The currently existing organization clients (clients that talk to the Switch API) will be removed and the integrators need to recreate them. This means that the integrations need to be updated with the new client IDs and client secrets to function properly and be able to fetch access tokens.

• The new organization clients will support only 1 client secret.

• The new organization clients will support rotating of the client secret. This would be possible to be done using the Switch portal or if automation is needed, the integrators can rotate the secrets using the Switch API endpoint for rotating secrets.

VTN credentials

• The currently existing VTN credentials (clients that talk to the OpenADR 3 VTN API) will be removed and the integrators need to recreate them. This means that the integrations need to be updated with the new client IDs and client secrets to function properly and be able to fetch access tokens.

• The new VTN credentials will support only 1 client secret.

• The VTN credentials will support rotating of the client secret. This would be possible to be done using the Switch portal or if automation is needed, the integrators can rotate the secrets using the Switch API endpoint for rotating secrets.