Adovo

Adobe Experience Cloud

Which Workfront Fusion AEM folder module still uses JWT?

Distinguish Fusion Create a Record from Create a Folder before changing AEM Assets credentials.

November 9, 2026

A Fusion scenario may say it creates an AEM folder, yet its connection form still asks for a private key. In a November 5 community exchange, the question assumed that every folder action shared the same authentication. An Adobe community manager clarified that Create a Record uses JWT and the MAC API, while Create a Folder uses OAuth server-to-server and the Folder API. The operation name in a scenario is not enough to identify the credential path.

Inventory the module, not just the outcome

Open each affected Fusion scenario and record the exact module name, connector version, connection fields, endpoint and technical account. Separate older Create a Record flows from Create a Folder flows. Adobe's AEM Assets module reference lists the connection options; compare that documentation with what the tenant actually displays before replacing credentials.

Adobe's JWT migration guide says Service Account JWT credentials have reached end of life. That is a reason to identify remaining JWT dependencies, not a reason to assume an OAuth-backed Create a Folder scenario will fail. The community reply specifically says the Create a Folder module is not affected by that deprecation.

Migrate with a functional test

For any genuinely JWT-backed path, plan a supported module or API replacement and confirm AEM permissions on the new technical account. Test folder creation in a non-production environment, then verify asset visibility and cleanup. Keep a rollback path until scheduled runs, error handling and permissions all behave as expected.

For an OAuth-backed path, document the credential owner, expiry and permission review; do not rotate a healthy connection solely because another module uses JWT.

Adovo’s view

The migration unit is the actual API call, not the workflow label. Trace each scenario to its module and credential before making a platform-wide decision. That turns an alarming deprecation notice into a finite, testable inventory.

Continue exploring

Adobe Experience Cloud

Workfront Fusion

A failed Fusion run can stop the scenario: alert on deactivation

Use Workfront Fusion execution data to distinguish a failed run from a scenario that has stopped and needs an owner.

Read more

Adobe Experience Cloud

AEM AssetsContent Advisor

AEM Content Advisor filters fail when metadata uses the wrong namespace

Diagnose HTTP 500 from AEM Content Advisor metadata filters before changing the authoring experience.

Read more

Adobe Experience Cloud

AEM AssetsContent Hub

AEM Content Hub migration starts with a user and workflow inventory

Test licensing, collection structure and librarian work before replacing Asset Share Commons.

Read more
Explore Adobe services →