when SecurityStamp is NULL AuthenticationManager.CreateIdentity throws NullArguementException


Using Identity 2.0 (not sure if its 2.0 specific though) when a user has a NULL SecurityStamp i get a NullArguementException when AuthenticationManager.CreateIdentity is called.

Seems that I have several users with a NULL SecurityStamp but its a only a tiny amount of the total users. Tried the sample project "PrimaryKeysConfigTest" and reproduced it setting NULL for the SecurityStamp column after registering a user.

Setting a random GUID string for the SecurityStamp column appears to fix the issue but not sure what the implications are for this.

Thanks :)
Closed Apr 16, 2014 at 9:42 PM by HaoK


suhasj wrote Mar 24, 2014 at 9:19 PM

The securitystamp should always have a value. This is resolved here https://aspnetidentity.codeplex.com/workitem/2080