KbA0056: M2M Users Authentication Change Guide

Kaizen API authentication is being upgraded. Following the update, different instances of Kaizen will require different Client IDs, Secrets and JWT tokens. Click here to learn more about the Client IDs and Secrets. The M2M/API authentication and Kaizen server authentication updates are not synchronous. The Kaizen Endpoints will be unaffected by this change.

The following things may need to be edited in order to receive data:

1. New Client IDs and Secrets will be provided by CopperTree. You will receive the email before the change is implemented, please reach out to CopperTree at customersolutions@coppertreeanalytics, if you did not receive an email with your new client ID and secret.
2. JWT tokens will need to be regenerated. If you pull data from both Kaizen and Kaizen-east, you will be provided 2 Client IDs and Secrets. Click here to read how to create new JWT tokens.
3. Create a parallel workflow with the new JWT token. When the update is implemented, you will be sent another email. The workflow can be swapped over to use the new token(s).