The "503: authenticator support missing" Nightmare. | Community
Skip to main content
P
prasanna-mohite
Level 2
June 14, 2023
Solved

The "503: authenticator support missing" Nightmare.

  • June 14, 2023
  • 3 replies
  • 1064 views

Hi Team,

 

For quite long, I have been facing this issue but never been able to resolve this using the solutions provided on the ELC forums here.

  1. Followed steps as given on - https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-16542.html?lang=en Repository compaction.
  2. Followed the steps as per the accepted answer on - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/http-error-503-authenticationsupport-service-missing-cannot/m-p/415600#M941
  3. deleted the folder crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit
  4. Checked the bundles, all are in active state.

Below is the configuration of my local dev env.
1. Win 11, 16gb i5
2. OpenJDK 11
3. AEM QUickstart 6.5.0 with 6.5.12 Service pack installed.
4. command I ma using to execute the JAR - java -Xmx2048M -agentlib:jdwp=transport=dt_socket,address=8888,server=y,suspend=n -jar cq-quickstart-6.5.0-author-p4502.jar

This issue I had been facing quite few times till date, and all the time I had to create a new instance wasting a lot of time. Now, even after creating a new instance, I am still getting the same issue on installing my project, clueless what to do.

 

KR,
Prasanna

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Sady_Rifat

    There is a permanent solution that can be done by org.apache.sling.jcr.repoinit.RepositoryInitializer~my-project.cfg.json file. After deleting this OSGI Config file it will be solved.
    Not sure, after 1st deployment, it will be solved or need to take a new instance.

     

    You need to try this. But after following your step 2 (deleting /author/crx-quickstart/repository/segmentstore/repo.lock & /author/crx-quickstart/launchpad/felix/cache.lock) and then deploying it will be solved permanently.

     

    Hope this helps you

    3 replies

    Sady_Rifat
    Community Advisor
    Sady_RifatCommunity AdvisorAccepted solution
    Community Advisor
    June 14, 2023

    There is a permanent solution that can be done by org.apache.sling.jcr.repoinit.RepositoryInitializer~my-project.cfg.json file. After deleting this OSGI Config file it will be solved.
    Not sure, after 1st deployment, it will be solved or need to take a new instance.

     

    You need to try this. But after following your step 2 (deleting /author/crx-quickstart/repository/segmentstore/repo.lock & /author/crx-quickstart/launchpad/felix/cache.lock) and then deploying it will be solved permanently.

     

    Hope this helps you

      EstebanBustamante
      Community Advisor and Adobe Champion
      EstebanBustamanteCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      June 14, 2023

      As mentioned by @sady_rifat the reason is the repoInit configuration, if you remove the whole config org.apache.sling.jcr.repoinit.RepositoryInitializer~my-project.cfg.json.  it will work. But if you still need this repoInit config for your project, you could switch the configuration to .config instead of cfg.json, that will solve the problem as well. 

      Esteban Bustamante
        P
        prasanna-mohiteAuthor
        Level 2
        June 15, 2023

        Hi @sady_rifat and @estebanbustamante : thanks for your replies. Both the solutions did work for me, thank you so much for your responses.

        I deleted my project specific RepositoryInitializer config from configMgr, since I was able to log into localhost:4502/system/console/configMgr, then I deleted the cache.lock and repo.lock files.

          Terms & ConditionsAccessibility statement

          Loading footer...