503 cq AuthenticationSupport service missing. Cannot authenticate request. | Community
Skip to main content
sai111
sai111
Level 2
December 18, 2018
Question

503 cq AuthenticationSupport service missing. Cannot authenticate request.

  • December 18, 2018
  • 13 replies
  • 21112 views

Hi ,

Instance am working when I opened today suddenly started stating AuthenticationSupport service missing. Cannot authenticate request.

I find all the bundles are active , status of Apache Sling Authentication Serviceorg.apache.sling.auth.core is active and I tried deleting index folder under crx-quickstart/repository and restarting the server but nothing worked ,

Startup is happening but still authentication error persists

18.12.2018 21:32:36.438 *ERROR* [qtp1998025192-167] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.

18.12.2018 21:32:36.438 *ERROR* [qtp1998025192-167] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.

Please help .. any pointers...Thanks in advance

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

13 replies

Show previous replies
W
Adobe Employee
WasilZeeAdobe Employee
Adobe Employee
January 5, 2019

You should find the latest good revision as mentioned on page[1] by using oak-run jar. Stop the instance, follow steps 1-6 and then try to bring up the instance.

Thanks

Wasil

[1] Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6.x

Gaurav-Behl
Gaurav-Behl
Level 10
January 5, 2019

The logs clearly indicate that the segment has gone missing, deleted or corrupted or converted to .bak file. You would need to restore segmentnodestore to a last known good configuration which was sometime before the crash happened. You mentioned that all bundles are active which means the issue is not something that could be fixed by just restarting bundles.

The repository backup should be taken so that you have the master copy for various reasons including if you plan to contact customer care in future. If you do not take a backup and perform a wrong step, there is a possibility the repository might be lost forever and would have to setup AEM from scratch.

A
Anonymous
October 19, 2021

You can re-run your aem instancy from console and as admin, try:

  1. Delete crs-quickstart folder.
  2. Open your console as administrator (that is important).
  3. Position yourself in your aem-sdk folder.
  4. Run the following command: 
    java -XX:MaxPermSize=256m -Xmx1024M -jar your-instance-name.jar
    I got that code from: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/deploying/deploy.html?lang=en 

That worked for me, i hope it works for you.

 
 
    Terms & ConditionsAccessibility statement

    Loading footer...