Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

Migration from JWT to OAuth Server-to-Server in AEM IMS integration

Avatar

Level 2

Hi folks,

If JWT authentication is deprecated for Adobe IMS integration in AEM as a Cloud Service, is there a migration path or documentation showing how to replace JWT with OAuth Server-to-Server in AEM code (for example, replacing ServicePrincipalCredentials with an OAuth-based flow)?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @NavyaVo,

Yes - Adobe has officially deprecated Service Account (JWT) authentication for IMS integrations. The recommended replacement is OAuth Server-to-Server credentials.

Migration steps for your reference:

  1. In Adobe Developer Console, create new OAuth Server-to-Server credentials for your AEM project.

  2. Update your AEM code to request access tokens using the new client ID, client secret, and technical account details instead of ServicePrincipalCredentials.

  3. Use Adobe’s IMS token endpoint:

    POST https://ims-na1.adobelogin.com/ims/token/v3
    Content-Type: application/x-www-form-urlencoded
    grant_type=client_credentials
    client_id=...
    client_secret=...
    scope=...
    
  4. Replace any JWT signing logic with a direct OAuth token request.

Reference:


Santosh Sai

AEM BlogsLinkedIn


View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @NavyaVo,

Yes - Adobe has officially deprecated Service Account (JWT) authentication for IMS integrations. The recommended replacement is OAuth Server-to-Server credentials.

Migration steps for your reference:

  1. In Adobe Developer Console, create new OAuth Server-to-Server credentials for your AEM project.

  2. Update your AEM code to request access tokens using the new client ID, client secret, and technical account details instead of ServicePrincipalCredentials.

  3. Use Adobe’s IMS token endpoint:

    POST https://ims-na1.adobelogin.com/ims/token/v3
    Content-Type: application/x-www-form-urlencoded
    grant_type=client_credentials
    client_id=...
    client_secret=...
    scope=...
    
  4. Replace any JWT signing logic with a direct OAuth token request.

Reference:


Santosh Sai

AEM BlogsLinkedIn