POCO's with the new ASP.NET Identity and MVC 5.0 + claims-based Identity

Question

With the new version of VS 2013 RTM and asp.net mvc 5.0, I’ve decided to try out a few things...

Needless to say, a lot has changed. For example, the new ASP.NET I

Answer 1

You want the UserManager from Microsoft.AspNet.Identity to do your security part such your users do not have to trust that you can handle your security information correctly.

Identity.Framework is just a datastore for the Identity stuff, you could create your own store instead if you dont want EF. I have created one that just stores information directly in a xml file. But I always come back to using Identity because I dont want to deal with encrypting and making sure I am up to date with stuff in the security department.