AEM Assets Author API in Developer Console Missing Server-to-Server OAuth for Fusion Connection | Community
Skip to main content
D
Deepikakhanna
Level 1
February 3, 2026
Question

AEM Assets Author API in Developer Console Missing Server-to-Server OAuth for Fusion Connection

  • February 3, 2026
  • 2 replies
  • 26 views

!--startfragment>

I want to use the AEM List Folder module in Workfront Fusion to fetch subfolder data. However, while creating the connection I keep getting a 400 error.

To troubleshoot, I went to the Adobe Developer Console, created a project, and added the AEM Assets Author API. But when I try to configure authentication, there is no option available for Server-to-Server OAuth.

Because of this limitation, I am unable to connect the module.

Could you please advise how to solve this problem, or if there is any alternative solution to connect Fusion with AEM Assets for listing folders?

!--endfragment>

    2 replies

    Avinash_Gupta_
    Community Advisor and Adobe Champion
    Avinash_Gupta_Community Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    February 3, 2026

    Hi ​@Deepikakhanna 

     

    Instead of going down the route of using the AEM Assets HTTP API, I would recommend using the OOB AEM Assets module available in Fusion. Here is the complete documentation that you can follow to configure it. The AEM Assets Module in Fusion have an option to get the listing of all the folders, which would be perfect for your use case. 

     

    https://experienceleague.adobe.com/en/docs/workfront-fusion/using/references/apps-and-their-modules/adobe-connectors/aem-assets-modules#get-a-folder-listing

      D
      DeepikakhannaAuthor
      Level 1
      February 4, 2026

      !--startfragment>

      Thanks, Avinash. I need the subfolder data in order to fetch the last modified date and all related details. However, when I use the List Folder module, I am not getting this information.

      !--endfragment>

      Vishal_Anand
      Vishal_Anand
      Level 4
      February 5, 2026

      ​@Deepikakhanna Here are few options to fix Workfront Fusion 400 when connecting to AEM Assets:

      Pre-requisite: 

      • Confirm you have IMS org admin or developer console admin rights (required to create Service Account/JWT).
      • Verify you added the correct AEM Assets API (Author) and not just generic AEM API.
      • If you’re targeting local SDK/author, Basic auth will work for testing.

      Preferred fix — use Adobe I/O Service Account (Server-to-Server JWT)

      • Ask your org admin (or use your admin account) to open Adobe Developer Console → Create Project → Add API → AEM Assets Author → Add Credentials → choose “Service Account (JWT)”.
      • Generate/download the private key JSON.
      • In AEM Cloud (or local SDK mapped to cloud integration), register the Adobe I/O integration and map the service account to AEM permissions (Cloud Manager / IMS configuration).
      • In Fusion, you cannot natively import JWT — instead build a small HTTP auth step (or middleware) that exchanges the JWT for an access token via Adobe IMS, then use that token in Fusion’s HTTP modules to call the AEM Assets List Folder API.

      Alternative immediate workarounds

      • For local testing: use Basic Auth in Fusion’s AEM module or HTTP module (username:admin) against your local AEM author.
      • Build a tiny proxy (Lambda, Heroku, or container) that does the Adobe I/O JWT flow and exposes a simple API key/token endpoint Fusion can call — Fusion calls proxy → proxy calls AEM.
      • Ask your Adobe admin to create the server-to-server integration and share credentials with Fusion team.

      Troubleshooting tips:

      • Capture the 400 response body in Fusion logs—often it shows “invalid_token” or “insufficient_scope”.
      • Test the API call with curl using the final token to confirm AEM responds before wiring Fusion.

      ​@kautuk_sahni 

      Terms & ConditionsAccessibility statement

      Loading footer...