Introducing ASP.NET Identity – A membership system for ASP.NET applications

Introducing ASP.NET Identity – A membership system for ASP.NET applications

Rate This
  • Comments 51

ASP.NET Identity is the new membership system for building ASP.NET web applications. ASP.NET Identity allows you to add login features to your application and makes it easy to customize data about the logged in user.

[Update] Please visit  ASP.NET Identity for getting the latest information about ASP.NET Identity project and learning more on how to get started and migrate from earlier membership systems.


Following are some of the feature of the ASP.NET Identity system

  • One ASP.NET Identity system
    • ASP.NET Identity can be used with all of the ASP.NET frameworks such as ASP.NET MVC, Web Forms, Web Pages, Web API and SignalR
  • Ease of plugging in profile data about the user
    • When you create new users in your application, it is now easy to add extra information about the user. For eg.. if you wanted to add a Birthdate option for users when they Register an account in your application.
    • ASP.NET Identity uses Entity Framework Code First and it is possible to extend the POCO classes.
  • Persistence control
    • By default the ASP.NET Identity system will store all the user information in a database. ASP.NET Identity uses Entity Framework Code First to implement all of its persistence mechanism.
    • If your application requirements are that this information might be stored in a different storage mechanism such as SharePoint, Azure Table Service, No Sql databases etc. it is now possible to plug in different storage providers.
  • Unit testability
    • ASP.NET Identity makes the web application more unit testable. You can write Unit Tests for the parts of your application that use ASP.NET Identity
  • Simple Role provider
    • There is a Simple Role providers which lets you restrict access to parts of your application by Roles. You can easily create Roles such as “Admin” and add Users to Roles.
  • Claims Based
    • ASP.NET Identity supports claims-based authentication, where the user’s identity is represented as a set of claims. There is a Claims
  • External Logins 
    • You can easily add external logins such as Microsoft Account, Facebook, Twitter and Google to your application store the user specific data in your application using this system.
    • You can also add login functionality using Windows Azure Active Directory and store the user specific data in your application using this system.

How do I get it?

ASP.NET Identity is used by ASP.NET Web Forms, MVC and SPA templates in Visual Studio 2013. it is also available as Nuget packages on the Nuget gallery

  • Nuget packages
    • Microsoft.Aspnet.Identity.Core
      • This package contains the core interfaces of ASP.NET Identity.
      • core
    • Microsoft.Aspnet.Identity.EntityFramework
      • This package contains the implementation of ASP.NET Identity system which works with Entity Framework. This means that if you use this package then you can store information in a Sql Server database.
      • ef 
  • VS 2013 preview
    • The ASP.NET Web Forms, MVC and SPA templates have 1.0.0-alpha1 version of ASP.NET Identity
  • ASP.NET and Web Tools 2013 Preview Refresh (Supports English version of VS2013 Preview only)
    • The ASP.NET Web Forms, MVC and SPA templates have 1.0.0-beta1 version of ASP.NET Identity
    • You can download the Preview refresh by clicking the above link
    • Following are the notable changes from 1.0.0-alpha1 – 1.0.0-beta1
      • In these templates you no longer need IdentityConfig.cs
      • Lots of public APIs were changed for renames and refactoring of code.
      • Transactions support was added to the framework.


Sample to add profile data

The following video video(mark 55min) gives you a sneak peak into the features.

You can download a sample from This is based on the ASP.NET MVC template that shipped with ASP.NET and Web Tools 2013 Preview Refresh (Supports English version of VS2013 Preview only) Once you have this Preview Refresh installed you can do the same for ASP.NET Web Forms and SPA applications.

Please do stay tuned to this blog for upcoming posts where I will dive into the various other features in this system.

Leave a Comment
  • Please add 3 and 4 and type the answer here:
  • Post
  • How can I get a list of all users to create an admin dashboard?

  • @LeusKapus: As of now there is no API that returns IQueryable type with list of either users or roles. For the current bits you need to use the DBContext class directly to get the list of users

  • @suhasbj Why there is no answer about the azure storage implementation? You don't have plans, time, is there a reason that it's not a good idea?

  • @Luiz Bicalho: I do agree that the Azure storage implementation is a good idea. I got in touch with the crew and there will be a sample for this which we will release as a Nuget package which the users can then build upon.

  • Understanding that you can't reference future release dates I'm wondering how things synch up now that VS2013 RTM _is released. Should we consider MVC5 as in RTM state? Is it Open Sourced? Any state changes to this version of the membership system (including docs) given the RTM state?

    much appreciated.

  • @am.steve: we released VS2013 RC. When The RTM version will be released, it will have the MVC5 RTM version. There are a couple of changes in the Identity API from RC to RTM but that will be fully documented in the RTM release. Majority of our web stack such as  MVC, Web API, Web Pages, SignalR is already sourced and you can get more information

Page 4 of 4 (51 items) 1234