Universal Editor status 302 to localhost:8443 | Community
Skip to main content
J
JaymeSantos
August 4, 2025

Universal Editor status 302 to localhost:8443

  • August 4, 2025
  • 2 replies
  • 586 views

Hi all,

I'm facing an issue with Universal Editor connecting to my local AEM Author. I'm following react headless tutorial with wknd boilerplate and running local-ssl-proxy --source 8443 --target 4502 / local-ssl-proxy --source 8001 --target 8000 /  node universal-editor-service.cjs as recommended. Even so, after added the data-aue-prop, data-aue-type, and data-aue-label (instrument-to-edit-content) the editor tries to fetch CF details from 8443 when selecting the "team members" component and get status 302 with no body to the following endpoints:

Still able to add, remove and edit the members and every property of the teams component. But for selecting a CF from the modal I have no options to DAM folders and the same 302 issue in the network console to the following endpoint:

When acessing any of those endpoints directly from the browser I get correct JSON in response.

Also, I have successfully fetch 8443 data from the frontend openned in UE. Seems the local instance is redirecting UE to the void. Is it a missing configuration? Any clue to solution?

2 replies

Karishma_begumSh
Karishma_begumSh
Level 4
August 6, 2025

Hi @jaymesantos 

1. Allow Anonymous Access to QueryBuilder
Go to: http://localhost:4502/system/console/configMgr/org.apache.sling.engine.impl.auth.SlingAuth
enticator
In Authentication Requirements, add:
- /bin/querybuilder.json
- /content/dam/my-project
2. Login on 8443
Visit https://localhost:8443 in browser
Login to AEM Author before launching UE
3. Use Better Proxy
Replace:
local-ssl-proxy --source 8443 --target 4502
With:
npx universal-editor-proxy --port 8443 --aem-author-port 4502
Try this and the CFs should appear in the picker.


Hope this helpful.:)

 

Regards,

Karishma.

    J
    JaymeSantosAuthor
    August 6, 2025

    universal-editor-proxy not found in npm registry 

    npx universal-editor-proxy --port 8443 --aem-author-port 4502 npm error code E404 npm error 404 Not Found - GET https://registry.npmjs.org/universal-editor-proxy - Not found npm error 404 npm error 404 'universal-editor-proxy@*' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: C:\Users\jayme.santos\AppData\Local\npm-cache\_logs\2025-08-06T12_18_51_378Z-debug-0.log

    Authentication Requirements option not found in http://localhost:4502/system/console/configMgr/org.apache.sling.engine.impl.auth.SlingAuth

    already authenticated from 8443

    i have also tried to follow instructions from https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/headless/universal-editor/introduction#configure-services

    but some of the services was not found as expected in configMgr, missing: `Adobe Granite Query Parameter Authentication Handler` and `Universal Editor URL Service`

    i have noted the following

    but unable to access `feature pack` url https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html?package=%2Fcontent%2Fsoftware-distribution%2Fen%2Fdetails.html%2Fcontent%2Fdam%2Faem%2Fpublic%2Fcq-6.5.21-universal-editor-1.0.0.zip

    i have the most recent aem sdk running, should `cq-6.5.21-universal-editor-1.0.0.zip` be installed in my instance? download it from where?

     

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      September 2, 2025

      @jaymesantos just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...