Universal Editor with classic AEM components

[daniel-strmecki]

Hi everyone,

I have a client requesting to migrate their existing, classic AEM components to Universal Editor (UE). They do not want EDS, just UE. Now I know it is not officially supported by Adobe, but given the universal nature of the UE, it should be technically possible. I was wondering if anyone has done it already, and if so, please share your learnings. I am especially interested in achieving the following without EDS:

1) How to enable asset picker and other UE integrations with AEM author via a Technical user account?

2) How to instruct a page template in AEM to open a page in UE instead of the classic Page Editor? Without adding a custom button.

3) Any other possible challenges I am not seeing ATM?

Thanks in advance,

Daniel

[daniel-strmecki]

Update: There seems to be an OOTB OSGi service called "Universal Editor URL Service", which I configured according to the documentation [1], but it's still NOT opening the page in Universal Editor.
[1] https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dev...

[daniel-strmecki · Accepted solution]

Got some help from my Adobe friends and was able to resolve this:

• Due to a bug in AEMaaCS 2025.5, the Universal Editor was temporarily disabled and under a feature flag

After Adobe set the feature flag, I had to provide the following config to get it working:

• org.apache.sling.engine.impl.SlingMainServlet.cfg.json

{
  "sling.additional.response.headers": [
    "X-Content-Type-Options=nosniff"
  ]
}

•  com.day.crx.security.token.impl.impl.TokenAuthenticationHandler.cfg.json

{
  "path": "/",
  "skip.token.refresh" : [
    "/libs/granite/csrf/token.json",
    "/mnt/overlay/granite/ui/content/shell/header/actions/pulse.data.json"
  ],
  "token.required.attr": "None",
  "token.encapsulated": false,
  "token.samesite.cookie.attr": "None"
}

• com.day.cq.wcm.core.impl.UniversalEditorURLServiceImpl.cfg.json

{
  "mappings": [
    "/content/demo:${author}${path}.html?login-token=${token}"
  ],
  "resourcetypes": [
    "demo/components/page"
  ]
}

Hope this helps someone in the future!