AEM unable to login | Community
Skip to main content
Anwar_Sadat
Anwar_Sadat
New Participant
October 16, 2015
Solved

AEM unable to login

  • October 16, 2015
  • 13 replies
  • 10449 views

Hi Experts,

We are running AEM 6.0 with SP2. After a recent restart of one of our publish instance, we are no longer able to login with admin credentials.

We keep getting the following error in the logs:

 

16.10.2015 13:49:40.262 *WARN* [qtp2074601335-30] org.eclipse.jetty.servlet.ServletHandler /libs/granite/core/content/login.html
java.lang.IllegalArgumentException: Invalid token ''
        at org.apache.jackrabbit.api.security.authentication.token.TokenCredentials.<init>(TokenCredentials.java:42)
        at com.day.crx.security.token.impl.TokenAuthenticationHandler.createCredentials(TokenAuthenticationHandler.java:578)
        at com.day.crx.security.token.impl.TokenAuthenticationHandler.extractCredentials(TokenAuthenticationHandler.java:352)
        at org.apache.sling.auth.core.impl.AuthenticationHandlerHolder.doExtractCredentials(AuthenticationHandlerHolder.java:75)
        at org.apache.sling.auth.core.impl.AbstractAuthenticationHandlerHolder.extractCredentials(AbstractAuthenticationHandlerHolder.java:60)
        at org.apache.sling.auth.core.impl.SlingAuthenticator.getAuthenticationInfo(SlingAuthenticator.java:697)
        at org.apache.sling.auth.core.impl.SlingAuthenticator.doHandleSecurity(SlingAuthenticator.java:452)
        at org.apache.sling.auth.core.impl.SlingAuthenticator.handleSecurity(SlingAuthenticator.java:438)
        at org.apache.sling.engine.impl.SlingHttpContext.handleSecurity(SlingHttpContext.java:121)

 

Any help in this regard is much appreciated !!!

 

Thanks,

Anwar

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by maxbarrass-anchora

    Correct answer to this question is to clear cookies, whatever is marked as "correct" is incorrect.

    13 replies

    Show previous replies
    smacdonald2008
    smacdonald2008
    New Participant
    October 16, 2015
    Was there any custom implementation or other changes done to your AEM instance that may account for the changed behaviour in the token?      
      Anwar_Sadat
      Anwar_SadatAuthor
      New Participant
      October 16, 2015

      Hi- Figured out that the authentication is successful. But the "login-token" cookie return by AEM is not valid.

      It is supposed to be like: login-token=4177bc3c-8d72-40e2-be47-bd6f93c1b5ae%3ad7bd26b3-cd48-4430-b7d7-d60fdecb2361_660c460ab31f8e8f%3acrx.default

      But it looks like this: login-token=117182c7-02d4-4c88-97b3-0714fa1ff3b2%3a<MISSING TOKEN>%3acrx.default

      Any idea why this could have happened and any remedies?

        Peter_Puzanovs
        Peter_Puzanovs
        New Participant
        October 16, 2015
                Right, well after recent restart something must have happened to your system. As this exception is not the most explanatory one check earlier in the logs for more meaningful hints to what has happened and why authentication does not want to work. Thanks, Peter
          Terms & ConditionsAccessibility statement

          Loading footer...