AEM 6.5.23 Universal Editor Issue on Dev | Community
Skip to main content
L
lax50
Level 2
March 2, 2026
Question

AEM 6.5.23 Universal Editor Issue on Dev

  • March 2, 2026
  • 1 reply
  • 26 views

Hi Everyone,
We are currently developing sample components for the AEM Universal Editor. While editing works as expected on local using a local universal editor service, we are encountering issues on the Dev environment when switching to the Global Adobe-managed service endpoint.
Specifically, we are seeing timeout and CORS errors related to the Universal Service, preventing the component from being configured. Since we are on AEM 6.5.23.

we added all the domain in the cors policy configuration still we got the error.

Has anyone successfully configured the global endpoint for AEM 6.5 ? Any insights would be appreciated.
below is the tag added in the head.html
<meta name="urn:adobe:aue:config:service" content="https://universal-editor-service.adobe.io"> ---pointing to global

for local 
<meta name="urn:adobe:aue:config:service" content="https://localhost:8080"> ---pointing to local

1 reply

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
March 2, 2026

Hi ​@lax50 ,
1. Don’t point meta to adobe.io directly: In head.html change to:

<script src="https://universal-editor-service.adobe.io/cors.js" async></script>

<meta name="urn:adobe:aue:system:aemconnection"
      content="aem65:https://<your-author-host>">

<meta name="urn:adobe:aue:config:service"
      content="https://<your-author-host>/universal-editor">

2. Dispatcher: proxy /universal-editor to Adobe

ProxyPass        "/universal-editor" "https://universal-editor-service.adobe.io"
ProxyPassReverse "/universal-editor" "https://universal-editor-service.adobe.io"

3. Dispatcher: CORS + OPTIONS

  • Allow OPTIONS on the author vhost.
  • Forward Origin, Access-Control-*, Authorization headers in clientheaders.any.

4. AEM CORS OSGi

In Adobe Granite CORS Policy:

  • alloworiginregexp: https://.*\.adobe\.com, https://.*\.adobe\.net, and your domains.
  • supportscredentials=true, supportedmethods includes OPTIONS, supportedheaders=*.

After these four steps, the global Universal Editor service will work on Dev without CORS/timeout errors.

Thanks,
Amit

Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
Terms & ConditionsAccessibility statement

Loading footer...