Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM 6.5.11 HTTP ERROR 503 AuthenticationSupport service missing.

Avatar

Level 5

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

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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/

 

View solution in original post

4 Replies

Avatar

Community Advisor

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

Try to check bundle status .

Avatar

Level 5

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

 

 

Avatar

Correct answer by
Employee Advisor

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/

 

Avatar

Level 4

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.