Adobe Experience Cloud
Workfront API access has a deadline beyond the login screen
Inventory custom Workfront OAuth clients before the February 2027 retirement; test their replacement identity and permissions.
November 18, 2026
A scheduled Workfront sync may still run today while the credential that powers it is nearing retirement. Adobe’s migration guide says new legacy custom OAuth2 apps could no longer be created after November 1, 2026, and existing apps stop working on February 1, 2027. The change concerns custom integrations using Workfront-issued client IDs, not ordinary user login or Adobe-managed Slack and Teams integrations.
Find the jobs behind each credential
Start in Workfront’s OAuth2 application list, then trace every client ID to its owner, scheduled scenario, script, vendor connector, and failure contact. Do not treat a healthy Fusion connection as proof that an unrelated custom script is covered. Adobe’s Workfront connection update separates reauthorizing existing Adobe connections from migrating custom OAuth2 applications. Put both on the inventory, with different owners.
Prove the new identity can do the same work
For a backend job, Adobe describes server-to-server authentication in Developer Console as the usual replacement. A user-facing app may need user authentication instead. The new technical account can begin with Contributor access, so a successful token request is only the first check. Run a representative read and write under the new identity against a test project. Confirm object visibility, access level, and the integration’s error handling when a token expires.
Cut over with a rollback window
Move one lower-risk job first. Compare its output with the old integration and watch the next scheduled run. Record who can rotate the new credential and where failure alerts go. Retire the old app only after the dependent jobs pass, leaving time before the service deadline for a permissions fix.
Adovo’s view
An integration is owned when someone can name its identity, its last successful business outcome, and its recovery path. A credential inventory is a continuity map, not an administrative spreadsheet.
