Server-side integrations with AEM as a Cloud Service (a build job, a content sync, an asset ingestion service) need a credential to call AEM. For years, the word “JWT” described how many of them got one. Adobe’s documentation now says “JWT” has three quite different statuses depending on where the credential was created, and that is where mistakes can creep in. This post separates them, summarizes what Adobe’s pages say about each, and flags what we could and couldn’t verify.
Three Situations, Three Different Statuses
| Where the credential lives | Status in Adobe’s pages | What the pages say |
| Adobe Developer Console projects using Service Account (JWT) credentials (for example Cloud Manager API integrations) | REMOVED | The Deprecated and Removed Features page (updated November 11, 2026) lists this exact item in its Removed table, with no date on that row. Adobe’s migration page says: “As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported,” and that they “will not work after current certificates expire or March 1, 2026, whichever is earlier.” Replacement named: the Adobe Developer Console’s S2S OAuth credentials. |
| AEM Developer Console JWT credentials (server-side calls to an AEM environment) | DEPRECATED, no removal date declared | The same page lists “AEM Developer Console JWT credentials” in its Deprecated table, with the replacement “AEM Developer Console Server-to-Server OAuth credentials. No removal date declared.” The 2026.10.0 release notes add that the JWT-style credentials “will be supported for the foreseeable future.” |
| OAuth Server-to-Server credentials in the AEM Developer Console | NEW. No GA/Beta label stated | Adobe’s AEM token page carries a callout: “OAuth Server-to-Server credentials in the AEM Developer Console are available starting November 4, 2026.” The page itself was last updated October 29, 2026 and states no maturity label. |
| Local development access token | For local testing only | A separate option in the AEM Developer Console. Not a substitute for a server integration credential. |
Two things to be careful about. First, “removed” and “deprecated” are different statuses, and they apply to different places: Adobe lists the Adobe Developer Console JWT credentials as removed, but the AEM Developer Console JWT credentials as deprecated with no removal date declared. Second, the new option is very new. Adobe’s page says Server-to-Server credentials in the AEM Developer Console became available on November 4, 2026, so most teams have little experience with it yet.

The three situations and what Adobe’s pages say about each.
Situation 1: AEM Developer Console Technical Accounts
This is the credential type most AEM-focused integrations use to make server-side calls to an AEM environment. Adobe’s page is explicit about the direction: “Use OAuth Server-to-Server credentials for server-side integrations. Service Account (JWT) credentials are deprecated in favor of OAuth Server-to-Server.” The page gives no removal date for JWT.
Creating a Server-to-Server account
- Where: the AEM Developer Console (not the Adobe Developer Console), under Integrations, creating a new technical account of the OAuth Server-to-Server type.
- Who can create one: per the page, users with an IMS organization administrator role who are also members of the AEM Users or AEM Administrators product profile on AEM Author. A user with the Environment administrator role can view details, but not the secret.
- What you get: a technical account with one active client secret, which you can download or copy. The page states a limit of up to 20 technical accounts, and deleted accounts count toward it.
- The secret is shown once: “The AEM Developer Console shows an OAuth Server-to-Server client secret only once.” Only the user who creates the account can see it, so that person must pass it on securely. If it is lost, create a new secret from an active one, or create a new technical account.
Getting and using a token
The page describes a client-credentials request to the IMS token endpoint, with the client ID, client secret, and scope. The response includes an access token, its type, and an expiry in seconds. No JWT signing, private key, certificate, or refresh token is needed. The access token is then sent as a bearer token on calls to the AEM environment. The page does not state a token lifetime in numbers; it says to use the expiry value returned and to cache and reuse the token until it is close to expiring. The page also provides examples and an optional Node.js helper (Node.js 18 or newer); we have not reproduced or tested them.
Permissions: the part that doesn’t carry over
“A valid IMS access token does not grant additional AEM permissions.”
“Permissions on the old technical account are not automatically transferred to the new account.”
So the work after creating the account is on the AEM side: add the technical account to a product profile in the Admin Console, let that profile synchronize as an AEM group, and configure that group’s permissions for the calls your integration makes. Adobe says to grant only the permissions needed and to call only resources the account is authorized to access.
Adobe’s migration steps
| Step | What Adobe’s AEM page says |
| 1. Create a Server-to-Server technical account | In the AEM Developer Console (not the Adobe Developer Console), go to Integrations, create a new technical account, and choose OAuth Server-to-Server as the credential type. |
| 2. Assign a product profile and AEM permissions | Add the technical account’s email to a product profile in the Adobe Admin Console. The page says the profile is “synchronized as an AEM group, with the technical account as a member.” Then set that group’s permissions on the author instance. |
| 3. Change the application | Switch the app to the client-credentials flow (no JWT signing, private key, certificate, or refresh token is needed). |
| 4. Verify | Confirm token generation and API calls work. |
| 5. Retire the old credential | “After all application instances use OAuth Server-to-Server, retire the old JWT credentials and delete the old technical account.” The page adds: “Do not remove the old account before the replacement integration is verified.” |
Situation 2: Adobe Developer Console Projects (Removed)
If your JWT credential lives in an Adobe Developer Console project (for example for Cloud Manager API integrations), Adobe’s Deprecated and Removed Features page lists these as removed, and its migration page gives dates that have all passed. Here is what that migration page says:
| Topic | What Adobe’s migration page says |
| Dates | Deprecation announced May 1, 2023; no new JWT credentials after June 3, 2024; end of life June 30, 2025; credentials will not work after current certificates expire or March 1, 2026, whichever is earlier. |
| What happens | After June 30, 2025 you cannot refresh certificates, and integrations “will stop working once existing certificates expire.” Adobe “will automatically convert Service Account (JWT) credentials to OAuth Server-to-Server credentials after certificates expire or on March 1, 2026 (whichever is earlier), breaking any integration still relying on the old credentials.” The page does not say whether a converted credential works with an integration’s existing code. |
| How migration works | On the JWT credential tab, use the migration card to add an equivalent OAuth Server-to-Server credential. It “has the same client id, technical account, connected APIs and services, scopes, and product profiles” as the old one, and “you can use either credential to generate access tokens” during the transition. During migration you cannot add any API or service to the project. |
| Before deleting the old credential | The UI checks conditions including whether the app has generated tokens with the new credential more recently than the old one, and whether it has been at least 24 hours since the old credential last generated a token. The page does not describe what the UI does if a check fails. |
| Irreversible steps | “Completion of this step on the Developer Console will complete the migration, and the step cannot be rolled back.” Cancelling the migration deletes the new OAuth credential, and an application already using it “will stop working.” |
| How current is it | The page shows no last-updated date, and every date on it has already passed. Check your project in the console rather than relying on the page. |
A caveat on this section. A search summary of Adobe’s AEM-specific JWT deprecation page suggested additional details (including how Adobe handles read-only projects that Cloud Manager creates automatically, and a statement that a JWT “utility” in the AEM Developer Console is not deprecated). When we tried to open that page directly, it returned an error, so we could not verify any of that and have not relied on it. The pages we could read call the AEM Developer Console JWT credentials deprecated. If you have read-only, automatically created projects, ask Adobe about their status.
Secrets and Rotation: What Adobe’s AEM Page Says
- “Do not put a client secret in browser-side code, mobile applications, source control, or logs. Treat access tokens as secrets as well.”
- Rotate secrets periodically and whenever one is exposed. The steps: create a new secret, switch applications to it, verify, then revoke the old one. “IMS requires at least one active secret.” The page says Server-to-Server credentials do not require annual certificate renewal.
- “Do not assume that revoking a secret immediately invalidates access tokens that were already issued.”
- Deleting the technical account “revokes the account and all of its client secrets in IMS immediately,” and “Account deletion cannot be undone.”
What We’d Do (Our Reading)
This is our interpretation, not Adobe guidance, and we have not migrated an integration ourselves.
- Inventory first. List every integration that calls AEM or Adobe APIs and note which of the three situations it falls under. The risk is treating them as one thing.
- Treat Adobe Developer Console JWT integrations as the urgent group. Adobe’s stated dates have passed, so check each project’s status in the console now rather than waiting for something to fail.
- Treat AEM Developer Console JWT accounts as planned work, not a fire drill. The docs say deprecated, supported “for the foreseeable future,” with no removal date. But the replacement only became available on November 4, 2026, so pilot it on a non-production environment first.
- Map permissions before cutover. Because permissions do not transfer, write down what the old technical account could do and recreate exactly that on the new group.
- Keep the old credential until the new one is proven. Adobe says not to remove the old account before the replacement is verified, and deletion cannot be undone.
- Plan secret storage and rotation up front. A secret that is shown once needs a proper place to live and a documented way to rotate it.
- Ask Adobe two questions: what the maturity label is for Server-to-Server in the AEM Developer Console, and whether a removal date for AEM Developer Console JWT credentials is planned.
What We Haven’t Verified
- We read Adobe’s pages on November 19, 2026. We have not created or migrated a credential in a live environment.
- We could not open Adobe’s AEM-specific JWT deprecation page (it returned an error), so nothing in this post depends on it.
- The Adobe Developer Console migration page shows no last-updated date, and its dates are all in the past. We do not know the current state of any particular project.
- Adobe states no GA/Beta label for Server-to-Server credentials in the AEM Developer Console, and we did not confirm one.
- We did not test token lifetime, the 20-account limit, or the permission sync behavior described in the page.
- We read the pages through a summarizing tool. Please check the quoted dates and statuses against the live pages before acting.
Checklist
- List every integration that authenticates to AEM or Adobe APIs, and note where each credential was created
- For Adobe Developer Console JWT projects, check each project’s status in the console now
- For AEM Developer Console JWT accounts, schedule migration and pilot Server-to-Server on a non-production environment
- Confirm who in your organization holds the IMS administrator and AEM product profile roles needed to create accounts
- Record the old account’s AEM permissions and recreate them on the new group
- Switch the application to the client-credentials flow and cache tokens until near expiry
- Verify token generation and API calls before touching the old credential
- Delete the old account only after verification (it cannot be undone)
- Store secrets outside source control and logs, and document a rotation process
- Ask Adobe about the maturity label and any planned removal date
Final Thoughts
When one word covers three different situations, the safest first move is to stop using the word and ask which situation you are in. Two of the three are straightforward: one is removed and needs checking today, one is only for local testing. The third, AEM Developer Console technical accounts, is where there is time but a clear direction. Use that time to pilot the new option on a non-production environment, map permissions carefully, and ask Adobe the questions its pages leave open.
Sources (Adobe documentation, read November 19, 2026)
- Generating Access Tokens for Server-Side APIs: experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/generating-access-tokens-for-server-side-apis
- Deprecated and Removed Features and APIs: experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/release-notes/deprecated-removed-features
- Migrating from Service Account (JWT) credential to OAuth Server-to-Server: developer.adobe.com/developer-console/docs/guides/authentication/ServerToServerAuthentication/migration
- Current Release Notes for AEM as a Cloud Service: experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/release-notes/release-notes/release-notes-current


