Skip to main content
DavidGevorgyan
Community Manager
Community Manager
Nov 16, 2026 9:52 AM UTC

Product update: Changes to Adobe Workfront auth connections

Workfront authentication is moving to Adobe sign-in

Workfront's legacy OAuth2 authentication is being retired in favor of Adobe identity (Adobe IMS / Experience Cloud sign-in). Two changes apply, depending on how you connect to Workfront.

  Connections (Fusion, Experience Platform, other Adobe solutions) Custom OAuth2 integrations (scripts, custom-built or third-party tools)
What's changing New and reauthorized connections sign in with your Adobe account instead of the Workfront OAuth2 application. Apps set up under Setup > System > OAuth2 are being retired. Integrations must authenticate through Adobe Developer Console (developer.adobe.com).
Action needed Reauthorize existing connections to move them to the new flow. Migrate each custom OAuth2 app to Adobe Developer Console.
Who acts Users and admins who own Workfront connections Workfront admins and integration owners

This doesn't change how you log in to Workfront. Adobe-managed integrations, such as the packaged Microsoft Teams and Slack integrations, are being migrated separately by Adobe.

Key dates

Date Milestone What it means for you
Now New connections use Adobe sign-in Existing connections keep working until reauthorized.
November 1, 2026 New custom OAuth2 app creation disabled You can no longer create custom OAuth2 apps in Workfront. Existing apps continue to work.
February 1, 2027 Legacy OAuth2 service retired Custom OAuth2 apps stop working. Integrations not yet migrated lose Workfront API access.

Why this matters

  • Unified credentials: One Adobe sign-in works across Adobe products and integrations.
  • Better security and SSO: Adobe IMS provides consistent identity controls and single sign-on.
  • Easier administration: Admins manage access and authentication policies in one place.

Before you begin

  • Inventory your Workfront connections and custom OAuth2 apps, and note which integration users, scheduled jobs, scenarios, and third-party tools depend on each.
  • Make sure whoever reauthorizes has an Adobe account (IMS / Experience Cloud) with the right permissions in both Adobe and Workfront.
  • Plan a maintenance window, and coordinate with owners of integration users to avoid interrupting scheduled operations.
  • Start with non-production connections and integrations to validate the new flow and any permission differences.

Reauthorize a Workfront connection

  1. Open the connection page where your Workfront connection is configured.
  2. Select the connection and choose Reauthorize.
  3. Sign in with your Adobe account, completing any MFA or SSO prompts.
  4. Accept any Workfront consent screens. The connection now uses Adobe sign-in.
  5. Run a test or sample job to verify.

Migrate a custom OAuth2 integration

Replace the Workfront-issued OAuth2 client ID and secret with credentials from Adobe Developer Console, then update the integration to use that authentication flow. Complete this before February 1, 2027.

Troubleshooting

  • Can't sign in with Adobe IMS: Confirm you have an active Adobe account and that your org's SSO configuration allows sign-in.
  • Missing Workfront permissions after reauthorizing: Confirm the Adobe account has the Workfront role or API scopes the integration needs.
  • Automations failing after reauthorizing: Check scheduled jobs and integration users for permission changes, then re-test.
  • Legacy flow still in use: It's deprecated and will stop working, so plan your migration now.

Documentation and support

We'd like your feedback, such as bulk reauthorization for org admins, a preflight permission checker, or automated migration notifications. Share it through the same channels.