undefined

Universal Editor fails to load legacy AEM Sites without EDS

Last update: Fri Feb 27 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Universal Editor fails to load target pages for legacy AEM Sites that don’t use Experience Data Service (EDS). The editor displays a login screen or error message instead of rendering the page. Universal Editor blocks authentication requests and fails to load pages that lack required Universal Editor instrumentation. To resolve the issue, use the correct Universal Editor entry point and instrument pages.

Description description

Environment

  • Product: Adobe Experience Manager as a Cloud Service (AEMaaCS) – Sites
  • Scenario: Legacy AEM Sites without Experience Data Service (EDS)

Issue/Symptoms

  • Universal Editor displays the AEM login screen in an iframe and doesn’t proceed to load the page.
  • The browser console logs the warning, Blocked autofocusing on an < input> element in a cross-origin subframe.
  • The network trace shows HTTP 403 errors for /_security_check requests when loading the page through Universal Editor.
  • The AEM Page Editor loads and renders the same pages correctly outside Universal Editor.

Resolution resolution

Follow these steps to address the issue:

  1. Access Universal Editor using the AEM author domain URL instead of experience.adobe.com. Open Universal Editor directly from the AEMaaCS author instance using a URL  https://author-pXXXXX-eYYYYYY.adobeaemcloud.com/ui#/@<org>/aem/universal-editor/canvas/author-pXXXXX-eYYYYYY.adobeaemcloud.com/content/your-site/...html to avoid blocked authentication requests.
  2. Instrument pages for Universal Editor by adding required scripts, meta tags, and data attributes. Follow the Universal Editor instrumentation guidelines in Adobe documentation to ensure Universal Editor loads and renders legacy AEM pages correctly.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f