Troubleshooting anti-forgery token problems

I don’t know if you mean you are able to get the error on demand – or you’re seeing it in your logs but in any case here’s a way to guarantee an antiforgery token error.

Wait for it…

  • Make sure you’re logged out, then enter your login
  • Double click on the login button
  • You’ll get :

The provided anti-forgery token was meant for user “”, but the current user is “[email protected]”.

(For now I’m going to assume that this exact error message changed in MVC4 and that this is essentially the same message you’re getting).

There’s a lot of people out there that still double click on everything – this is bad! I just figured this out after just waking up so how this got through testing I really don’t know. You don’t even have to double click – I’ve got this error myself when I click a second time if the button is unresponsive.

I just removed the validation attribute. My site is always SSL and I’m not overly concerned about the risk. I just need it to work right now. Another solution would be disabling the button with javascript.

This can be duplicated on the MVC4 initial install template.

Leave a Comment