...it's me...eRiCk

Well, Server Error in '/' Application. Value cannot be null. Parameter name: value Description:  An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details:  System.ArgumentNullException: Value cannot be null. Parameter name: value Source Error: Line 431: { Line 432: AuthenticationManager.SignOut(DefaultAuthenticationTypes.ExternalCookie); Line 433: var identity = await UserManager.CreateIdentityAsync(user, DefaultAuthenticationTypes.ApplicationCookie); Line 434: AuthenticationManager.SignIn(new AuthenticationProperties() { IsPersistent = isPersistent }, identity); Line 435: It happened because when i created the user using Configuration Seed (i'm using EF Code First), i'm not filled the Security Stamp that is why the error occured because when the Security Stamp is null, it...

Hi, Long time no post, i will try to post again since i came out searching a typical solution over and over again :D Now i'm gonna post about session. Since i got this from other link so here it is So I started looking into the IIS settings and came to know that i missed two things to change : Application pool’s Idle Time-out (minutes) Session state  – State server’s Time-out (seconds) Once I have changed above settings than after Session timeout worked. So after that I have made one checklist that can help us to validate Session timeout settings, here i am sharing it with you as well so that you will also get some benefits from it : Application Pool  – Advanced Settings Menu – Process Model – Idle Time-out (minutes) Sites –  Session State  – Cookie Settings – Time-out (minutes) If you are using  State Server  or  SQL Server  to manage your session (instead of InProcess), Here is the steps to follow :    ...