I'm not sure this will help but check if the "service.bundleLocation" property in <sling.home>/config/org/apache/sling/engine/impl/auth/SlingAuthenticator.config contains the correct version. This might not be a problem anymore but I think I had problem with this a while back when the value of " service.bundleLocation" didn't match the one installed in Sling (the value contained the version number in the name of the jar/bundle). One way to test this is to 1. Shutdown Sling 2. Rename <sling.home>/config/org/apache/sling/engine/impl/auth/SlingAuthenticator.config 3. Start sling 4. Enter http://<your server>/system/console/configMgr 5. Modify some config value of Apache Sling Authentication Service and save the new config 6. Check if the new <sling.home>/config/org/apache/sling/engine/impl/auth/SlingAuthenticator.config contains another "service.bundleLocation" value
I'm not even sure if the version mismatch in "service.bundleLocation" can cause a problems but at least it is something to check out. /Pontus Tue Nov 11 2014 at 9:37:44 AM skrev Geoff Capper <[email protected]>: > Hi All, > > I have had to rebuild my installation of Sling 6 which is installed as a > war file on Tomcat, as the server crashed. I've got back to the stage > where Sling is installed and running, and I can use the admin side of it > to examine the installed bundles etc. > > When I try to access the explorer I get a "HTTP Status 503 - > AuthenticationSupport service missing. Cannot authenticate request." error. > > In the logs the first warning is: > org.apache.sling.jcr.jackrabbit.server.impl.security. > PluggableDefaultAccessManager > No pluggable AccessManager available, falling back to DefaultAccessManager > > All references to this problem I've seen in searching indicate it's a > result of other things failing, like lucene or the repository, but there > are no errors in the logs related to these. > > Can anyone offer any advice? > > Thanks, > Geoff >
