AEM 6.5 HTTP 503 Error AuthenticationSupport service missing. Cannot authenticate request | Community
Skip to main content
April 2, 2021

AEM 6.5 HTTP 503 Error AuthenticationSupport service missing. Cannot authenticate request

  • April 2, 2021
  • 3 replies
  • 8671 views

Hello Members,

I have a AEM 6.5 OSGi framework on-premise Author and Publisher instances running in Windows OS. It was working fine for a long time. We took a snapshot of the Windows server and we used the Window's Services to restarted the Author and Publisher instances. The Publisher instance is running fine, but the Author instance is not. The error.log in Author instance shows the following error:

19.03.2021 15:27:41.963 *ERROR* [qtp1031644809-61] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request. 19.03.2021 15:27:41.964 *ERROR* [qtp1031644809-61] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.

The URL to server:port/aem/start.html displays the following error message in the browser:

HTTP ERROR 503 Problem accessing /aem/start.html. Reason: AuthenticationSupport service missing. Cannot authenticate request.

The link to crx  -  http://server:port/crx/de/index.jsp is displaying the following error:

HTTP ERROR 503 Problem accessing /crx/de/index.jsp. Reason: Service Unavailable

http://server:port/crx/packmgr/index.jsp gives the following error:

Problem accessing /crx/packmgr/index.jsp. Reason:

AuthenticationSupport service missing. Cannot authenticate request.

I do see that the Author's crx-quickstart/repository only has cache, diff-cache and index folders. It does not have the segmentstore, datastore and blobids folders, but these 3 folders exist in the Publisher instance.

I did try to rename the index folder and restarted the Author instance, but it did not create a new index folder. The user has full permissions to the folder.

Our team tried to revert back to previous state by using the snapshot and server backup from last month, but the issue is the same.

I can access the /system/console/memoryusage and it uses only 10% of memory.

The below links work in Author and all the bundles are active. The login is like a pop-up near the browser tab, and it is not the usual login page that is used to access these links.

 http://server:port/system/console/slinglog

 http://server:port/system/console/bundles

1. Is there any suggestion on what to try next to recover from this issue.

2. Are the segmentstore, datastore and blobids folders needed in Author's crx-quickstart/repository? If yes, is it possible to upload specific packages or drop it in a specific folder structure

3. Are there any specific steps to be taken to backup crx repository when server is backed up, or a snapshot is taken?

Thanks in advance for the response,

Leena

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

3 replies

Asutosh_Jena_
Community Advisor
Community Advisor
April 3, 2021

Hi @aemuser001 

Please follow the below steps:

  1. Shutdown the instance.
  2. Delete all index from the index folder.(\crx-quickstart\repository\index)
  3. Restart the AEM instance.

This should resolve the issue.

 

Thanks!

April 5, 2021

Hi Asutosh, I tried your suggestion to stop the instance, removed the folders within index folder and start it again. Now the following error is displayed when accessing server:port/aem/start.html :

HTTP ERROR 404

Problem accessing /aem/start.html. Reason:

Not Found

 

Any suggestion?

Thanks,

Leena

Love_Sharma
September 30, 2022

For future visitors, Last time when I saw this error was when I was trying to switch between AEM 6.3 and AEM 6.5 instance. 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. 

 

chandracq
October 21, 2022

This may or may not be relevant but might help somebody.

 

We cloned AEM from Prod 6.4.8 2012  Win 2012 to lower environment  Win 2019.  upgraded from 6.4.8 to 6.5.15 and also upgraded Oracle Java 8.21 to Zulu 11 64 Bit.

Everything worked fine with java 8 but as soon as sa i switched to Java 11.. it was giving an HTTP 503/500 error.

 

After several hours of investigation, i found there was an unused JAAS Authentication configuration sitting in OSGI for many years, was not getting executed in Java 8 but it was executed in JAVA 11. 

 

I switched back to Java 8 and cleaned that and switched back to 11 and all works consistently 

 

Regards,

Chandra