6

Sitecore logs are showing lot of these messages: WARN The current user cannot be resolved from the authentication cookie. The cookie will be removed.

Ex:
    Line 556: 1820 07:14:48 WARN  The current user cannot be resolved from the authentication cookie. The cookie will be removed.
    Line 1680: 6612 08:02:06 WARN  The current user cannot be resolved from the authentication cookie. The cookie will be removed.
    Line 1681: 6916 08:02:06 WARN  The current user cannot be resolved from the authentication cookie. The cookie will be removed.

We are using mixed authentication : Asp net membership provider + Sitecore virtual user. We recently upgraded from Sitecore 7.2 to Sitecore.NET 8.1 (rev. 160519) and are using Mongo DB as well for gathering Analytics data.

Any suggestions to identify the issue? I verified on the server and there aren't any app pool recycles when this happened.

  • 1
    this might happen when the cookie can't be parsed properly. For example, you might have changed the machine key or if you have many CDs with different machine keys or your CDs are not sticky balanced. – Andrey Bobrov Dec 20 '16 at 16:15
  • Yes we have three CD Servers but none of them have the machine Keys in the config files and I verified that load balancer has sticky sessions enabled. – Vamshi Dec 20 '16 at 19:20
  • it is defined in the machine config on the instance. Check if they are the same – Andrey Bobrov Dec 21 '16 at 18:16
  • 1
    @PeteNavarra - Nope it doesn't... Probably that's the issue!!! I'll change it on Tuesday and will let you know the results... Thanks much Pete.. – Vamshi Dec 23 '16 at 0:55
  • 1
    Also I raised a ticket with Sitecore today. I'll post the response as soon as I hear back from them as well... Thanks everyone.. – Vamshi Dec 23 '16 at 0:56
2

I've seen this error when logged in to the Sitecore backoffice and then attempting to log into the site as a front-end member in the same browser.

I don't believe Sitecore can handle this situation gracefully by default and logs this error.

Haven't looked at the core code but likely this is likely due to multiple identities on the same auth ticket and Sitecore blindly grabbing the first.

Can you confirm if this is your scenario? Or do you see this error when logging in on separate browsers too?

| improve this answer | |
  • I could see this error when logging in on separate browsers too... Between in CD servers we disabled Sitecore login and CM server is in a different server. – Vamshi Dec 27 '16 at 14:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.