august 4, 2023

New OAuth credentials are here! What partners need to know.

Learn how to migrate to the new OAuth Server-to-Server credential and the migration timeline 

Adobe recently introduced a new OAuth Server-to-Server credential that replaces existing Adobe Service Account (JWT) credentials. The new credential will make it easier to develop and maintain Adobe applications and integrations.

The new OAuth Server-to-Server credentials are based on OAuth 2.0 client credentials grant type and work out of the box using standard OAuth2 libraries. Because the new credentials do not use public-private certificate key pairs when generating access tokens, they remove the need to rotate certificates periodically.

Many Adobe partners are using Service Account (JWT) credentials generated from an Adobe customer’s Developer Console. To ensure uninterrupted service, partners must update their software to support the new OAuth Server-to-Server credential, and then work with their Adobe customers to migrate the Service Account (JWT) credentials to new OAuth Server-to-Server credentials in each customer’s Adobe Experience Cloud environment. Adobe will disallow the creation of new Service Account (JWT) credentials on May 1, 2024 (see the detailed timeline below).

Deprecation Timeline    

Please note the following deadlines for migrating to the new credential.

May 1, 2023 – Apr 30, 2024

May 1, 2024 – Dec 31, 2024 
Jan 1, 2025 (end of life) 

Existing applications.

Existing applications using Service Account (JWT) credentials continue to work. 

Existing applications using Service Account (JWT) credentials continue to work. 

Existing applications using Service Account (JWT) credentials will stop working.  

New applications 

New applications can use Service Account (JWT) credentials. 

New applications cannot use Service Account (JWT) credentials anymore. 

New applications cannot use Service Account (JWT) credentials anymore. 

The migration process is simple and enables a zero-downtime migration. To learn more, view our documentation:

Partners who have questions should contact their respective support team:

Was this article helpful? 
Share it: