ASP.NET Identity provider that users MongoDB for storage

ASP.NET MVC 5 shipped with a new Identity system (in the Microsoft.AspNet.Identity.Core package) in order to support both local login and remote logins via OpenID/OAuth, but only ships with an Entity Framework provider (Microsoft.AspNet.Identity.EntityFramework).

02-11-2014 - [http://blogs.msdn.com/b/webdev/archive/2014/02/11/announcing-preview-of-microsoft-aspnet-identity-2-0-0-beta1.aspx](Microsoft has released Microsoft.AspNet.Identity v2 Beta 1). I will be addressing these issues and introducing them into the MongoDB.AspNet.Identity provider.

• Drop-in replacement ASP.NET Identity with MongoDB as the backing store.
• Requires only 1 mongo document type, while EntityFramework requires 5 tables
• Contains the same IdentityUser class used by the EntityFramework provider in the MVC 5 project template.
• Supports additional profile properties on your application's user model.
• Provides UserStore implementation that implements the same interfaces as the EntityFramework version:
  • IUserStore
  • IUserLoginStore
  • IUserRoleStore
  • IUserClaimStore
  • IUserPasswordStore
  • IUserSecurityStampStore

These instructions assume you know how to set up MongoDB within an MVC application.

1. Create a new ASP.NET MVC 5 project, choosing the Individual User Accounts authentication type.
2. Remove the Entity Framework packages and replace with MongoDB Identity:

Uninstall-Package Microsoft.AspNet.Identity.EntityFramework
Uninstall-Package EntityFramework
Install-Package MongoDB.AspNet.Identity

3. In ~/Models/IdentityModels.cs:
   • Remove the namespace: Microsoft.AspNet.Identity.EntityFramework
   • Add the namespace: MongoDB.AspNet.Identity
   • Remove the ApplicationDbContext class completely.
4. In ~/Controllers/AccountController.cs
   • Remove the namespace: Microsoft.AspNet.Identity.EntityFramework
   • Add the connection string name to the constructor of the UserStore. Or empty constructor will use DefaultConnection

public AccountController()
{
    this.UserManager = new UserManager<ApplicationUser>(
        new UserStore<ApplicationUser>("Mongo");
}

The UserStore has multiple constructors for handling connection strings. Here are some examples of the expected inputs and where the connection string should be located.

UserStore(string connectionNameOrUrl)

UserStore("Mongo")

web.config

<add name="Mongo" connectionString="Server=localhost:27017;Database={YourDataBase}" />

UserStore(string connectionNameOrUrl)

UserStore("Mongo")

web.config

<add name="Mongo" connectionString="mongodb://localhost/{YourDataBase}" />

OR

UserStore(string connectionNameOrUrl)

UserStore("mongodb://localhost/{YourDataBase}")

Special thanks to David Boike whos RavenDB AspNet Identity project gave me the base for jumpstarting the MongoDB provider