Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

The "503: authenticator support missing" Nightmare.

Avatar

Level 2

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-authenticat...
  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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

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

Avatar

Community Advisor

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 projectyou could switch the configuration to .config instead of cfg.json, that will solve the problem as well. 



Esteban Bustamante

Avatar

Level 2

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.