Towards the end of last week ASP.NET Identity 2.0 was released. ASP.NET Identity has been developed with the following goals:
- To provide a single framework that will work with all of the ASP.NET frameworks, such as ASP.NET MVC, Web Forms, Web Pages, Web API, and SignalR.
- To give the user control over the schema of user and profile information.
- To allow users to write unit test against parts of the application that use ASP.NET Identity.
- To make it OWIN compatible. ASP.NET Identity uses OWIN authentication for managing users of a web application. This means that instead of using FormsAuthentication to generate the cookie, the application uses OWIN CookieAuthentication.
- To support claims-based authentication, which allows developers to be a lot more expressive in describing a user’s identity than membership roles.
- To allow user to be authenticated using their social log-ins such as using Microsoft Account, Facebook, Twitter, Google, and others.
- And to enable ASP.NET team to have rapid release cycles, by making ASP.NET Identity available as a NuGet package.
Lately, I was in conversation with our QA lead, which made us realize of an issue that, certainly will cause inconvenience to the end users of the web application on which we are working on. Although the issue is very much common and is to be faced by all web developers, though it came late to me, I would defend myself by saying, ‘better late than never’.
Now the problem,