Getting an error AuthenticationSupport service missing. Cannot authenticate request.

[Nikhil2288]

I had some issue with one maven build and so I deleted my crx-quickstart and re-run again and since then I am unable to run the jar. Its stuck in between and browser throws an error - "

HTTP ERROR 503

Problem accessing /. Reason:

    AuthenticationSupport service missing. Cannot authenticate request.

"

Logs error : 23.06.2020 10:39:34.057 *ERROR* [qtp1050376747-74] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
23.06.2020 10:39:34.058 *ERROR* [qtp1050376747-74] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
23.06.2020 10:45:08.388 *ERROR* [qtp1050376747-72] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
23.06.2020 10:45:08.388 *ERROR* [qtp1050376747-72] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.

Can someone pls help? I verified OSGI bundles and everything is active.

[Himanshu_Singhal · Accepted solution]

A few times what happens is that when you try to access (let's say) http://localhost:4502/sites.html it shows the following error as described by you. However, System Console works fine. Having such scenario, what you can do is just go to http://localhost:4502/crx/de and login there. Once you'll do the login, you shall be able to access all portals. 
Give it a try. 
I hope I've understood your problem correctly. If not, please walk me in right direction.

[vanegi]

This looks like the different authentication handlers might be in a race condition and whoever registers first might be blocking another from registering.

As for the error "AuthenticationSupport service missing. Cannot authenticate request" is this happening during startup? Because it's fine if it's during startup since the repository is not fully initialized yet.

You can check:

- AEM error.log

- Also confirm if you see segment not found error [1] along with AuthenticationSupport service missing error as that would confirm repository corruption if any. As the latter one is just a symptom but not an actual issue.

- Any recent changes after which you started to see repository corruption in all your instances ? I hope your instances are gracefully started and stopped each time.

[1]: https://helpx.adobe.com/in/experience-manager/kb/fix-inconsistencies-in-the-repository-when-segmentn...

[arunpatidar]

Make sure you have all the bundles are active.
Can you try without installing any custom code?