默认情况下,VS 2015中的ASP.NET身份使用字符串作为AspNet ***表的主键。我想改用int-typed id。经过一些研究后发现,开箱即用的框架支持不同类型的id。在下面的答案中,我将展示为实现这一目标所做的改变。
更新:在添加我的回答后,我在asp.net网站上发现了这篇博文,描述了相同但更全面的内容:http://www.asp.net/identity/overview/extensibility/change-primary-key-for-users-in-aspnet-identity
答案 0 :(得分:35)
IdentityModels.cs
更改为:
// New derived classes
public class UserRole : IdentityUserRole<int>
{
}
public class UserClaim : IdentityUserClaim<int>
{
}
public class UserLogin : IdentityUserLogin<int>
{
}
public class Role : IdentityRole<int, UserRole>
{
public Role() { }
public Role(string name) { Name = name; }
}
public class UserStore : UserStore<ApplicationUser, Role, int,
UserLogin, UserRole, UserClaim>
{
public UserStore(ApplicationDbContext context): base(context)
{
}
}
public class RoleStore : RoleStore<Role, int, UserRole>
{
public RoleStore(ApplicationDbContext context): base(context)
{
}
}
// You can add profile data for the user by adding more properties to your ApplicationUser class, please visit http://go.microsoft.com/fwlink/?LinkID=317594 to learn more.
public class ApplicationUser : IdentityUser<int, UserLogin, UserRole, UserClaim>
{
public DateTime? ActiveUntil;
public async Task<ClaimsIdentity> GenerateUserIdentityAsync(ApplicationUserManager manager)
{
// Note the authenticationType must match the one defined in CookieAuthenticationOptions.AuthenticationType
var userIdentity = await manager.CreateIdentityAsync(this, DefaultAuthenticationTypes.ApplicationCookie);
// Add custom user claims here
return userIdentity;
}
}
public class ApplicationDbContext : IdentityDbContext<ApplicationUser, Role, int,
UserLogin, UserRole, UserClaim>
{
public ApplicationDbContext()
: base("DefaultConnection")
{
}
public static ApplicationDbContext Create()
{
return new ApplicationDbContext();
}
}
在`App_Start \ IdentityConfig.cs中,更改以下类:
public class ApplicationUserManager : UserManager<ApplicationUser, int>
{
public ApplicationUserManager(IUserStore<ApplicationUser, int> store)
: base(store)
{
}
public static ApplicationUserManager Create(IdentityFactoryOptions<ApplicationUserManager> options, IOwinContext context)
{
var manager = new ApplicationUserManager(new UserStore(context.Get<ApplicationDbContext>()));
// Configure validation logic for usernames
manager.UserValidator = new UserValidator<ApplicationUser, int>(manager)
{
AllowOnlyAlphanumericUserNames = false,
RequireUniqueEmail = true
};
// Configure validation logic for passwords
manager.PasswordValidator = new PasswordValidator
{
RequiredLength = 8,
// RequireNonLetterOrDigit = true,
RequireDigit = true,
RequireLowercase = true,
RequireUppercase = true,
};
// Configure user lockout defaults
manager.UserLockoutEnabledByDefault = true;
manager.DefaultAccountLockoutTimeSpan = TimeSpan.FromMinutes(5);
manager.MaxFailedAccessAttemptsBeforeLockout = 5;
// Register two factor authentication providers. This application uses Phone and Emails as a step of receiving a code for verifying the user
// You can write your own provider and plug it in here.
manager.RegisterTwoFactorProvider("Phone Code", new PhoneNumberTokenProvider<ApplicationUser, int>
{
MessageFormat = "Your security code is {0}"
});
manager.RegisterTwoFactorProvider("Email Code", new EmailTokenProvider<ApplicationUser, int>
{
Subject = "Security Code",
BodyFormat = "Your security code is {0}"
});
manager.EmailService = new EmailService();
manager.SmsService = new SmsService();
var dataProtectionProvider = options.DataProtectionProvider;
if (dataProtectionProvider != null)
{
manager.UserTokenProvider =
new DataProtectorTokenProvider<ApplicationUser, int>(dataProtectionProvider.Create("ASP.NET Identity"));
}
return manager;
}
}
// Configure the application sign-in manager which is used in this application.
public class ApplicationSignInManager : SignInManager<ApplicationUser, int>
{
public ApplicationSignInManager(ApplicationUserManager userManager, IAuthenticationManager authenticationManager)
: base(userManager, authenticationManager)
{
}
public override Task<ClaimsIdentity> CreateUserIdentityAsync(ApplicationUser user)
{
return user.GenerateUserIdentityAsync((ApplicationUserManager)UserManager);
}
public static ApplicationSignInManager Create(IdentityFactoryOptions<ApplicationSignInManager> options, IOwinContext context)
{
return new ApplicationSignInManager(context.GetUserManager<ApplicationUserManager>(), context.Authentication);
}
}
在App_Start\Startup.Auth.cs
将OnValidateIdentity
属性更改为:
OnValidateIdentity = SecurityStampValidator.OnValidateIdentity<ApplicationUserManager, ApplicationUser, int>(
validateInterval: TimeSpan.FromMinutes(30),
regenerateIdentityCallback: (manager, user) => user.GenerateUserIdentityAsync(manager),
getUserIdCallback: id => id.GetUserId<int>())
更改ManageController以使用新的pk类型:
将User.Identity.GetUserId()
的所有条目替换为User.Identity.GetUserId<int>()
可能会有一些字符串id
参数需要更改为int
,但这就是它。
答案 1 :(得分:11)
使用ASP.NET核心标识的每this blog post进行以下更改:
首先,转到Data\Migrations
文件夹并删除其中的所有内容。
在Startup.cs
中,在ConfigureServices
方法中,将services.AddIdentity
更改为
services.AddIdentity<ApplicationUser, IdentityRole<int>>()
.AddEntityFrameworkStores<ApplicationDbContext, int>()
.AddDefaultTokenProviders();
在ApplicationDbContext.cs
中将基类从IdentityDbContext<ApplicationUser>
更改为
public class ApplicationDbContext
: IdentityDbContext<ApplicationUser, IdentityRole<int>, int>
最后,将ApplicationUser.cs
中的基类从IdentityUser
更改为
public class ApplicationUser : IdentityUser<int>
然后运行add-migration -o Data\Migrations
和update-database
。如果迁移导致任何问题,请使用VS中的Sql Server Management Studio或SqlServerObjectExplorer删除数据库(不仅使用文件系统),重新删除迁移,然后重试。 / p>