AspNet.Identity.RavenDB: Fully asynchronous, new and sweet ASP.NET Identity implementation for RavenDB
A while back, ASP.NET team has introduced ASP.NET Identity, a membership system for ASP.NET applications. Today, I'm introducing you its RavenDB implementation: AspNet.Identity.RavenDB.
29 November 2013
4 minutes read
Related Posts
A while back, ASP.NET team has introduced ASP.NET Identity, a membership system for ASP.NET applications. If you have Visual Studio 2013 installed on you box, you will see ASP.NET Identity Core and ASP.NET Identity Entity Framework libraries are pulled down when you create a new Web Application by configuring the authentication as "Individual User Accounts".
After creating your MVC project, you will see that you have an AccountController which a completely different code from the previous project templates as it uses ASP.NET Identity.
You can find tons of information about this new membership system from ASP.NET Identity section on official ASP.NET web site. Also, Pranav Rastogi (a.k.a @rustd) has a great introduction video on ASP.NET Identity which you shouldn't miss for sure.
One of the great features of ASP.NET Identity system is the fact that it is super extensible. The core layer and the implementation layer (which is Entity Framework by default) are decouple from each other. This means that you are not bound to Entity Framework and SQL Server for storage. You can implement ASP.NET Identity on your choice of storage system. This is exactly what I did and I created AspNet.Identity.RavenDB project which is fully asynchronous, new and sweet ASP.NET Identity implementation for RavenDB. You can install this library from NuGet:
PM> Install-Package AspNet.Identity.RavenDB
Getting started with AspNet.Identity.RavenDB is also really easy. Just create an ASP.NET MVC application from scratch by configuring the authentication as "Individual User Accounts". Then, install the AspNet.Identity.RavenDB package. As the default project is set to work with ASP.NET Identity Entity Framework implementation, you need to make a few more tweak here and there to make it work with RavenDB.
First, open the IdentityModels.cs file under the "Models" folder and delete the two classes you see there. Only class you need is the following ApplicationUser class:
public class ApplicationUser : RavenUser { }
As the second step, open up the AccountController.cs file under the "Controllers" folder and have delete the first constructor you see there. Only constructor you need is the following one:
public AccountController(UserManager<ApplicationUser> userManager)
{
UserManager = userManager;
}
Now you should be able to build the project successfully and from that point on, you can uninstall the Microsoft.AspNet.Identity.EntityFramework package which you don't need anymore. Lastly, we need to provide an instance of UserManager<ApplicationUser> to our account controller. I'm going to use Autofac IoC container for that operation to inject the dependency into my project. However, you can choose any IoC container you like. After I install the Autofac.Mvc5 package, here how my Global class looks like inside Global.asax.cs file:
using AspNet.Identity.RavenDB.Stores; using AspNetIndetityRavenDb.Models; using Autofac; using Autofac.Integration.Mvc; using Microsoft.AspNet.Identity; using Raven.Client; using Raven.Client.Document; using Raven.Client.Extensions; using System.Reflection; using System.Web.Mvc; using System.Web.Optimization; using System.Web.Routing; namespace AspNetIndetityRavenDb { public class MvcApplication : System.Web.HttpApplication { protected void Application_Start() { AreaRegistration.RegisterAllAreas(); FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters); RouteConfig.RegisterRoutes(RouteTable.Routes); BundleConfig.RegisterBundles(BundleTable.Bundles); const string RavenDefaultDatabase = "Users"; ContainerBuilder builder = new ContainerBuilder(); builder.Register(c => { IDocumentStore store = new DocumentStore { Url = "http://localhost:8080", DefaultDatabase = RavenDefaultDatabase }.Initialize(); store.DatabaseCommands.EnsureDatabaseExists(RavenDefaultDatabase); return store; }).As<IDocumentStore>().SingleInstance(); builder.Register(c => c.Resolve<IDocumentStore>() .OpenAsyncSession()).As<IAsyncDocumentSession>().InstancePerHttpRequest(); builder.Register(c => new RavenUserStore<ApplicationUser>(c.Resolve<IAsyncDocumentSession>(), false)) .As<IUserStore<ApplicationUser>>().InstancePerHttpRequest(); builder.RegisterType<UserManager<ApplicationUser>>().InstancePerHttpRequest(); builder.RegisterControllers(Assembly.GetExecutingAssembly()); DependencyResolver.SetResolver(new AutofacDependencyResolver(builder.Build())); } } }
Before starting up my application, I expose my RavenDB engine through http://localhost:8080. and I'm all set to fly right now. The default project template allows me to register and log in the application and we can perform all those actions now.
The same sample application available inside the repository as well if you are interested in: AspNet.Identity.RavenDB.Sample.Mvc.
The current ASP.NET Identity system doesn't provide that many features which we require in real world applications such as account confirmation, password reset but it provides us a really great infrastructure and the UserManager<TUser> class saves us from writing bunch of code. I'm sure we will see all other implementations of ASP.NET Identity such as MongoDB, Windows Azure Table Storage, etc. from the community.
Hey, I'm Tugberk 👋
Coder 👨🏻💻, Speaker 🗣, Author 📚, ex-Microsoft MVP 🕸, Blogger 💻
I live in London, UK 🏡
