ASP.NET Identity System in Visual Studio 2013 - New Feature

In this post you will learn about a very new enhancement in ASP.NET Framework technologies (MVC, Web Forms, Web Pages, Web API and SignalR) known as ‘ASP.NET Identity System’ with the release of Visual Studio 2013. This enhancement well defines the meaning of ‘One ASP.NET’, because this can be used with all ASP.NET Framework technologies more easily than before.

ASP.NET Identity System is a new Membership system for building ‘One ASP.NET’ applications. It allow us to add login features to our application and makes it easy to customize data about the logged in user. The whole Membership system is re-written by ASP.NET team to support ‘One ASP.NET’ goal, don’t worry earlier membership systems including ‘Simple Membership provider’ is still supported, if you want to migrate them then here is a nice KB for you by ASP.NET Team.

You can learn more about this new feature here.


Now, let’s look at all the features of ASP.NET Identity System:

One ASP.NET Identity System

This cool new ‘ASP.NET Identity’ can be used with all of the ASP.NET Frameworks including MVC, Web Forms, Web Pages, Web API and SignalR. In Visual Studio 2013 IDE when we do File | New Project (.NET 4.5) | we see ‘ASP.NET Web Application’ as a parent project template and under this we get option to pick project types from MVC, Web Forms, Web Pages, Web API, SignalR and for all this one identity will be supported.



Easily plug more profile data about the user

What about adding user’s first name, last name, date of birth etc while creating new user account in the application? It was really difficult before to add these extra information while registering new user. Now, with ASP.NET Identity System, it is easy to add extra information about the user. ASP.NET Identity uses Entity Framework Code First and it is possible to extend the POCO classes.

Persistence Control

ASP.NET Identity System uses Entity Framework Code First to implement all of its persistence control to store user information in databases such as SharePoint, Azure Table Service, No Sql databases etc. Now, we can easily plug in different storage providers which was quite a painful task before.

Unit Testability

ASP.NET Identity System makes the web application more unit testable. Now we can write Unit Tests for the parts of our application that use ASP.NET Identity.

Claims Based

ASP.NET Identity supports claims-based authentication, where the user's identity is represented as a set of claims.

External/Social Logins

This is one of the main reason in re-writing the membership system. Today we are looking more on social networks and wishing to extend the ability of our application to allow logins with Microsoft, Facebook, Twitter, Google, Yahoo accounts and even login using Windows Azure Active Directory and store user data in our application. So, this ASP.NET Identity System is well designed to enable these functionality.


NuGet Packages

With Visual Studio 2013, these bits are already included with templates but in case if you migrating your existing application then you can download the bits from NuGet. You need to install these two packages:-

Microsoft.Aspnet.Identity.Core - This package contains the core interfaces of ASP.NET Identity.

Microsoft.Aspnet.Identity.EntityFramework - This package contains the implementation of ASP.NET Identity System which works with Entity Framework Code First. This means that if you use this package then you can store information in a SQL Server database. Also we can easily plug other databases if we wanted.

Hope this helps.
Thanks.

Comments

  1. UnknownThursday, December 05, 2013 1:46:00 am

    Hi, Abhimannu this is really nice article. Thanks to share.

    ReplyDelete
  2. PRABHACARESunday, February 16, 2014 2:59:00 am

    Very informative!
    Abhimanyu, Thanks for sharing it.

    ReplyDelete

Post a Comment

Popular posts from this blog

Migrating database from ASP.NET Identity to ASP.NET Core Identity

Image
As you know ASP.NET Core Identity (table structure) is different from what we had earlier in ASP.NET Identity. Actually the identity system which we have today with .NET Core is very mature and continuously evolved be it ASP.NET Membership, ASP.NET Identity 1, ASP.NET Identity 2 and now ASP.NET Core Identity. Recently I had to migrate few application to ASP.NET Core and similar its identity database. Because the table schema is changed, i had to re-think and create migration script which I would like to share with you today. It is very simple and easy, just three step and I had everything ready: STEP 1 : Change name of existing tables STEP 2 : Create ASP.NET Core Identity tables STEP 3 : Migrate data from old tables (ASP.NET Identity) to new tables (ASP.NET Core Identity) Script:  https://gist.github.com/itorian/c699e8534b392a6c726ec66c48100072 You should also watch my video, where I demoed migration.
Read More »

Customize User's Profile in ASP.NET Identity System

Image
Note: You should read this post instead, I found below walkthrough will not work on ASP.NET Identity 2. I will re-work on this post soon. In this post you will learn how to customize User’s Profile and add some more fields like FirstName, LastName, EmailID etc with ASP.NET Identity System. In my last post I listed some of the great new features introduced with Identity system .
Read More »

Lambda two tables and three tables inner join code samples

In this blog post you will learn inner join using lambda queries. There will be two samples, in first sample you will see how you can join two tables and in second sample you will see how you can extend even further to join three tables and so on. I will sample in-memory data, but the same implementation will work with IQueryable (lazy query) too. Here's the code snippet:- namespace ConsoleApp1 {     class Program     {         static void Main()         {             var table1 = new List<Table1>();             table1.Add( new Table1 { Id = 1, Name = "Name 1" , Address = "Address 1" });             table1.Add( new Table1 { Id = 2, Name = "Name 2" , Address = "Address 2" });             table1.Add( new Table1 { Id = 3, Name = "Name 3" , Address = "Address 3" });             table1.Add( new Table1 { Id = 4, Name = "Name 4" , Address = "Address 4" });   
Read More »