This is a migrated thread and some comments may be shown as answers.

ASP.NET Identity 2.x provider

4 Answers 164 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

This question is locked. New answers and comments are not allowed.

4 Answers, 1 is accepted

answered on 24 Oct 2014, 06:50 PM

I've posted an article on how to convert from the standard Entity Framework implementation that's added when creating a templated ASP.NET web project: http://kaliko.com/blog/aspnet-template-for-data-access-identity/

I noticed that it's requires a few more steps than the MySQL implementation to get it up and running with the sample code that comes with the templated web project. Much due to the fact that I chose to use Guids as identifiers rather than strings which require the identifier data type to be specified in many calls.

General usage is much more straight forward, the following sample creates a role if it not exist and assign a user to it:

using AspNet.Identity.DataAccess;

using Microsoft.AspNet.Identity;

...

var roleManager = new RoleManager<IdentityRole, Guid>(new RoleStore());

var roleName = "MyGroup";

var role = roleManager.FindByName(roleName);

if (role == null) {

role = new IdentityRole(roleName);

roleManager.Create(role);

}

var userManager = new UserManager<IdentityUser, Guid>(new UserStore());

var user = userManager.FindByName("MyUser");

if (user != null) {

userManager.AddToRole(user.Id, roleName);

}