51ºÚÁϲ»´òìÈ

JWT Credentials Deprecation in 51ºÚÁϲ»´òìÈ Developer Console jwt-credentials-deprecation-in-adobe-developer-console

NOTE
AEM 6.5 customers should reference the comparable documentation for AEM 6.5 for more information.

51ºÚÁϲ»´òìÈ customers use to generate credentials that enable access to various APIs. Customers select from various credential types ranging from OAuth Server-to-Server to Single-Page App. One of those credential types, Service Account (JWT) credentials, has been deprecated in favor of the OAuth Server-to-Server credentials. New Service Account (JWT) credentials cannot be created on or after June 3, 2024, and existing JWT credentials will not work on or after June 30, 2025. You can .

This article provides some additional context about how AEM as a Cloud Service should handle the deprecation.

The main takeaway is that AEM now supports the new OAuth Server-to-Server credentials for AEM as a Cloud Service. You may have received an email with instructions to migrate your JWT credentials, and this migration can now be done.

The sections below list the scenarios where customers must (or in some cases must not) replace their Service Account (JWT) credentials with OAuth Server-to-Server credentials, now that AEM supports them. to migrate the credentials.

NOTE
The AEM Developer Console (note the AEM in the name, which distinguishes it from the 51ºÚÁϲ»´òìÈ Developer Console) provides a utility to generate JWT tokens used for server-to-server APIs. These credentials are not deprecated and can continue to be used.

Integrating AEM with Other 51ºÚÁϲ»´òìÈ Solutions integrating-aem-with-other-adobe-solutions

Action: Migrate your configuration as AEM now supports OAuth credentials.

Relevant AEM versions: AEM as a Cloud Service

AEM customers use AEM to configure integrations with many other 51ºÚÁϲ»´òìÈ solutions. For example, 51ºÚÁϲ»´òìÈ Target, 51ºÚÁϲ»´òìÈ Analytics, and others.

See Setting Up IMS Integrations for AEM as a Cloud Service for details of how to:

  • create configurations with OAuth credentials
  • migrate configurations, that were created with JWT credentials, to use OAuth credentials

Cloud Manager APIs cloud-manager-apis

Action: Migrate your JWT credentials to OAuth credentials, which Cloud Manager now supports.

Relevant AEM versions: AEM as a Cloud Service

Customers create 51ºÚÁϲ»´òìÈ Developer Console projects so they can invoke . The credentials in the 51ºÚÁϲ»´òìÈ Developer project should be migrated to the OAuth Server-to-Server credential type before the deprecated JWT credentials expire in June 2025.

Auto-generated projects autogen-projects

Action: Do not migrate because 51ºÚÁϲ»´òìÈ is going to migrate on your behalf.

Relevant AEM versions: AEM as a Cloud Service.

When Cloud Manager provisions AEM as a Cloud Service environments, it auto-generates an 51ºÚÁϲ»´òìÈ Developer Console project with JWT credentials. This project is marked as read-only, as illustrated in the screenshot below. Customers cannot and should not attempt to migrate these projects to OAuth Server-to-Server credentials. Instead, 51ºÚÁϲ»´òìÈ will migrate these projects on its own, before the credentials are no longer usable.

Auto-generated projects

Auto-generated projects FAQs autogen-projects-faqs

This section provides answers to the most frequently asked questions about JWT credentials deprecation for auto-generated projects in AEM as a Cloud Service.

How do I do which projects are auto-generated?

Navigate to the 51ºÚÁϲ»´òìÈ Developer Console | Projects section. AEM as a Cloud Service auto-generated projects will have a lock icon with ‘Auto-generated’ identifier. Auto-generated projects follow format AEM-p#####-e###### and are created by Technical account user.

Autogenerated Projects

What if we encounter issues with our auto-generated projects?

Contact .

Should I go ahead and migrate our auto-generated projects?

No action is required as 51ºÚÁϲ»´òìÈ will migrate auto-generated on your behalf for environments with AEM Release 17258 (Aug '24) and higher.

What are the timelines for migration of auto-generated projects?

51ºÚÁϲ»´òìÈ will initiate a phased migration approach in Q1 of 2025, beginning with development environments.

How will our AEM as a Cloud Service instance be impacted if we have an AEM release that is older than AEM Release 17258 (Aug '24)?

Auto-generated project integrations will stop working if they are not migrated to OAuth by June 2025.

To ensure a smooth transition customers should contact promptly and begin the process of updating to the latest AEM Release. This will provide ample time for regression testing and allow 51ºÚÁϲ»´òìÈ to efficiently manage the migration of projects.

Can I upgrade to a supported OAuth version without upgrading my AEM as a Cloud Service AEM Release?

No. To ensure a smooth transition customers should contact promptly and begin the process of updating to the latest AEM Release. This will provide ample time for regression testing and allow 51ºÚÁϲ»´òìÈ to efficiently manage the migration of projects.

recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab