Not using One ASP.NET Identity

[ghost]

MembershipProvider is an abandoned system now; Microsoft is now pushing their ASP.NET Identity solution (http://asp.net/identity).

SecurityGuard still looks to be the most complete user management system available right now for ASP.NET MVC. But unfortunately it's not particularly useful for greenfield projects where ASP.NET Identity is used instead of MembershipProvider.

Are there plans to make a migration? (It may require a rewrite of most of the back-end.)

[kahanu]

@jdavis-demark - you are right. I have written an article about the future of SecurityGuard exactly for these reasons. http://www.mvccentral.net/s/75

Because of the way the new OWIN system works, there doesn't seem to be a need for a UI to manage those credentials, but if you still want users to register in your own database, SecurityGuard can still be a good tool. Take a look at my article and let me know if you have any comments.

Thanks.

[DanRegalia]

I can still use this to manage roles and users tho, right? Maybe I'm missing out on something, but Identity doesn't have any way to manage Roles and Users built into it that I have been able to find.

[kahanu]

@DanRegalia - SecurityGuard works just with the System.Web.Providers framework. It does not work with the OWIN or Identity frameworks because they have a different architecture. If you use it as it is designed, it will work. If you want to use it with one of the previously mentioned frameworks above, then it will not work.

I hope this answers your question.