AEM restart issue. AuthenticationSupport service missing. Cannot authenticate request. | Community
Skip to main content
A
apoorva_arza
October 31, 2020
Solved

AEM restart issue. AuthenticationSupport service missing. Cannot authenticate request.

  • October 31, 2020
  • 4 replies
  • 27975 views

I am facing the classic HTTP error 503 while restarting my AEM instance.

Error logs state the following

Possible reason is missing repository service. Check AuthenticationSupport dependencies

 

I have checked that my bundle "Apache Sling Authentication Service (org.apache.sling.auth.core)" is active

I have followed the steps mentioned in this post

I have given the instance a good one hour to start completely

None of the above steps helped fix my issue.

 

Please suggest any methods you're aware of to troubleshoot this issue. I'm so stuck.

 

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 pat-lego

I had the same issue it was caused by a custom repoinit script that was deployed under crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit that was causing the repository service to fail on start. Most likely the activate function is runnig the repoinit scripts and silently dying.

 

 

Best thing to do is remove any custom repoinit scripts and restart the instance. If you have multiple of them the just delete them one at a time, but leave the OOTB ones there.

4 replies

ChitraMadan
Community Advisor
ChitraMadanCommunity Advisor
Community Advisor
October 31, 2020

Hi @apoorva_arza ,

 

Try to delete below 2 files and restart the instance:

 

/author/crx-quickstart/repository/segmentstore/repo.lock

/author/crx-quickstart/launchpad/felix/cache.lock

 

If this also don't work, try deleting the index folder and restarting again, which will build your indexes again and might take some time to start.

 

    A
    apoorva_arzaAuthor
    October 31, 2020

    Hi @chitramadan, thanks for your answer. The above two solutions did not work for me unfortunately.

      arunpatidar
      Community Advisor
      arunpatidarCommunity Advisor
      Community Advisor
      November 1, 2020

      I did not do anything, just deleted below file and it works.
      /author/crx-quickstart/launchpad/felix/cache.lock

       

      Arun Patidar
        saibul
        saibul
        Level 4
        July 9, 2021

        /publish/crx-quickstart/launchpad/felix/cache.lock doesn't help me

         

          Vijayalakshmi_S
          Vijayalakshmi_S
          Level 10
          November 2, 2020

          Hi @apoorva_arza,

          Please check all the available existing error.log files(logs rotated with previous days) in your local instance before you get to notice the exact log statement - "AuthenticationSupport service missing".

          Share the initial statement that logged as "Error" level. 

          Recently ran into the issue in one of my local instance and the original/initial cause was  Java Heap Space (java.lang.OutOfMemoryError: Java heap space) which then eventually lead to "AuthenticationSupport service missing" - While setting up the new instance, I missed to configure the JVM options in start.bat and was using the default one.

            R
            Adobe Employee
            rukshang822Adobe Employee
            Adobe Employee
            January 25, 2022

            I have the same error. Running AEM 6.5.X on a Windows 2016 server. The AEM instance was working fine until a reboot was performed (i am assuming AEM was not stopped properly before rebooting). Any advice? I have followed few steps identified in this blog (i.e delete Index folder, cache.lock,repo.lock) but problem is still there.

             

            ERROR: 

            HTTP ERROR 503 AuthenticationSupport service missing. Cannot authenticate request.
            URI: /
            STATUS: 503
            MESSAGE: AuthenticationSupport service missing. Cannot authenticate request.
            SERVLET: org.apache.felix.http.base.internal.dispatch.DispatcherServlet-42506205

             

            ERROR LOG:

            25.01.2022 02:19:43.188 *ERROR* [qtp1356185641-59] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
            25.01.2022 02:19:43.188 *ERROR* [qtp1356185641-59] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
            25.01.2022 02:19:43.330 *ERROR* [qtp1356185641-62] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
            25.01.2022 02:19:43.330 *ERROR* [qtp1356185641-62] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
            25.01.2022 02:19:44.704 *ERROR* [qtp1356185641-59] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
            25.01.2022 02:19:44.704 *ERROR* [qtp1356185641-59] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
            25.01.2022 02:19:46.406 *ERROR* [qtp1356185641-62] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
            25.01.2022 02:19:46.406 *ERROR* [qtp1356185641-62] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
            25.01.2022 02:19:49.450 *WARN* [sling-default-5-health-com.adobe.granite.queries.impl.hc.QueryLimitsHealthCheck] com.adobe.granite.queries.impl.hc.QueryLimitsHealthCheck Could not retrieve QueryEngineSettings MBean.

              S
              SaidaRaoGampala
              April 28, 2022

              I had the same issue it was caused by a custom repoinit script that was deployed under crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit that was causing the repository service to fail on start. Most likely the activate function is runnig the repoinit scripts and silently dying.

               

               

              Best thing to do is remove any custom repoinit scripts and restart the instance. If you have multiple of them the just delete them one at a time, but leave the OOTB ones there.


              I had the same issue. We have installed ServicePack12 on top of AEM 6.5 jar. And when we install our Maven archetype project to AEM instance and whenever we restart our AEM instance on local environment we are seeing a 503 Authentication Support missing error. I tried all the resolutions provided in this thread, but nothing worked.

                S
                sateeshkreddy
                Level 3
                June 30, 2023

                I had a similar issue. I have resolved this by activating all the bundles into active. in the system bundles, I saw a few are resolved. I have manually updated those as active and now it started working.

                Terms & ConditionsAccessibility statement

                Loading footer...