AEM 6.5.11 HTTP ERROR 503 AuthenticationSupport service missing. | Community
Skip to main content
A
arvind-1
Level 5
March 28, 2022
Solved

AEM 6.5.11 HTTP ERROR 503 AuthenticationSupport service missing.

  • March 28, 2022
  • 3 replies
  • 6869 views

Hi Team,

 

AEM Version: 6.5.11

 

Arc type used : 33

 

After every re-start, we get this error:

 

HTTP ERROR 503 AuthenticationSupport service missing. Cannot authenticate request.

URI:STATUS:MESSAGE:SERVLET:

/aem/start.html
503
AuthenticationSupport service missing. Cannot authenticate request.
org.apache.felix.http.base.internal.dispatch.DispatcherServlet-34738d2e

 

 

Regards,

AP

 

Best answer by joerghoh

I recently wrote a blog post specifically for that issue. As it is a very broad topic with a lot of possible reasons, I just outlined the most popular reasons:

 

https://cqdump.joerghoh.de/2022/03/17/how-to-analyze-authentication-support-missing/

 

3 replies

Himanshu_Jain
Community Advisor
Himanshu_JainCommunity Advisor
Community Advisor
March 28, 2022

Are you able to open /crx/explorer or /system/console .

Try to check bundle status .

Himanshu Jain
    A
    arvind-1Author
    Level 5
    March 28, 2022

    Hello All,

     

    We have got the root cause of this issue.

     

    Maven archtype 33 causes this issue. 

     

     

    Here is the link:

     

    Solutions:

     

    1) So, we need to use other version.

     

        OR 

    2) With same archtype 33, we need to fix repo init osgi config script 

    as below :

     

    https://github.com/adobe/aem-project-archetype/issues/852

     

    Regards,

    AP

     

     

      joerghoh
      Adobe Employee
      joerghohAdobe EmployeeAccepted solution
      Adobe Employee
      March 29, 2022

      I recently wrote a blog post specifically for that issue. As it is a very broad topic with a lot of possible reasons, I just outlined the most popular reasons:

       

      https://cqdump.joerghoh.de/2022/03/17/how-to-analyze-authentication-support-missing/

       

        Love_Sharma
        Love_Sharma
        Level 4
        September 30, 2022

        Deleting repoinit folder from my AEM instance fixed this issue for me. Either you can run below command

         rm -rf crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit OR delete the folder manually. 

        Blog post which Jorg mentioned, also talk about repoinit as one of the reason for getting this error.

          Terms & ConditionsAccessibility statement

          Loading footer...