Expand my Community achievements bar.

SOLVED

AEM 6.5.11 | Access failing modules- Cannot login

Avatar

Level 2

Hi community
Seeking advice 

We are constantly getting

HTTP ERROR 403 Forbidden

URI:	/libs/granite/core/content/login.html
STATUS:	403
MESSAGE:	Forbidden
SERVLET:	org.apache.felix.http.base.internal.dispatch.DispatcherServlet


Logs show: 

11.04.2022 05:19:42.716 *DEBUG* [qtp663498912-58] org.apache.sling.auth.core.impl.HttpBasicAuthenticationHandler forceAuthentication: Not forcing authentication because request parameter sling:authRequestLogin is not set
11.04.2022 05:19:42.716 *DEBUG* [qtp663498912-58] org.apache.sling.auth.core.impl.SlingAuthenticator getAuthenticationInfo: no handler could extract credentials; assuming anonymous
11.04.2022 05:19:42.716 *DEBUG* [qtp663498912-58] org.apache.sling.auth.core.impl.SlingAuthenticator doHandleSecurity: No credentials in the request, anonymous
11.04.2022 05:19:42.718 *INFO* [qtp663498912-58] org.apache.sling.auth.core.impl.SlingAuthenticator handleLoginFailure: Unable to authenticate anonymous user: Login Failure: all modules ignored
11.04.2022 05:19:42.718 *DEBUG* [qtp663498912-58] org.apache.sling.auth.core.impl.SlingAuthenticator handleLoginFailure: LoginException on an anonymous resource, fallback to getAnonymousResolver
11.04.2022 05:19:42.719 *DEBUG* [qtp663498912-58] org.apache.sling.auth.core.impl.SlingAuthenticator setAttributes: ResourceResolver stored as request attribute: user=anonymous


There has been no recent change with respect to com.adobe.granite.auth.saml.SamlAuthenticationHandler.config. This just started failing one fine day.

I was earlier able to restart cq5 from the instance but now even that's not working. Unable to access console to debug

Getting 

Authentication Failed

for all endpoints.


Need guidance on what could have caused this + how to fix




 

1 Accepted Solution

Avatar

Correct answer by
Level 2

Hi,
I was unable to login anywhere. Our author is behind dispatcher.

What we figured was that adding sling.auth.anonymous.user=“” was causing an issue. We logged in directly to the system using basic auth, reverted this change and it worked.

 

We were trying this configuration to solve an issue with our SAML but that's a separate issue.

View solution in original post

2 Replies

Avatar

Community Advisor

Hi,

Are you able to login using crx or package manager screen?

Do you have author behind dispatcher or CDN?



Arun Patidar

Avatar

Correct answer by
Level 2

Hi,
I was unable to login anywhere. Our author is behind dispatcher.

What we figured was that adding sling.auth.anonymous.user=“” was causing an issue. We logged in directly to the system using basic auth, reverted this change and it worked.

 

We were trying this configuration to solve an issue with our SAML but that's a separate issue.