Blazor中修改ASP.NET Identity用户主键（用户名改邮箱）

1. 自定义Identity用户实体 #

创建自定义用户类，将主键与邮箱绑定，同时同步用户名与邮箱，避免身份验证冲突：

public class ApplicationUser : IdentityUser<string>
{
    // 让主键Id直接映射为邮箱
    public override string Id
    {
        get => Email;
        set => Email = value;
    }

    // 同步用户名与邮箱，消除默认用户名的独立约束
    public override string UserName
    {
        get => Email;
        set => Email = value;
    }
}

2. 更新DbContext配置 #

修改项目的ApplicationDbContext，配置用户表的主键规则与字段约束：

public class ApplicationDbContext : IdentityDbContext<ApplicationUser>
{
    public ApplicationDbContext(DbContextOptions<ApplicationDbContext> options)
        : base(options)
    {
    }

    protected override void OnModelCreating(ModelBuilder builder)
    {
        base.OnModelCreating(builder);

        // 配置用户表主键为Id（即邮箱）
        builder.Entity<ApplicationUser>()
            .HasKey(u => u.Id);
        
        // 强制邮箱非空且唯一
        builder.Entity<ApplicationUser>()
            .Property(u => u.Email)
            .IsRequired()
            .HasMaxLength(256);
        
        // 移除用户名的唯一约束，避免与邮箱重复校验冲突
        builder.Entity<ApplicationUser>()
            .HasIndex(u => u.UserName)
            .IsUnique(false);
    }
}

3. 配置Identity服务 #

在Program.cs中更新Identity服务，指定使用自定义用户实体，并开启邮箱登录相关配置：

// 注册自定义Identity服务
builder.Services.AddDefaultIdentity<ApplicationUser>(options => options.SignIn.RequireConfirmedAccount = true)
    .AddEntityFrameworkStores<ApplicationDbContext>();

// 配置用户与登录选项
builder.Services.Configure<IdentityOptions>(options =>
{
    options.User.RequireUniqueEmail = true;
    options.SignIn.RequireConfirmedEmail = true; // 按需开启邮箱验证
});

// 配置Cookie认证路由
builder.Services.ConfigureApplicationCookie(options =>
{
    options.LoginPath = "/Login";
    options.ReturnUrlParameter = "returnUrl";
});

4. 调整Blazor登录组件 #

修改登录页面，将输入项改为邮箱，并在登录逻辑中使用邮箱作为凭证：

<EditForm Model="@loginModel" OnValidSubmit="@HandleLogin">
    <DataAnnotationsValidator />
    <ValidationSummary />

    <div class="mb-3">
        <label class="form-label">邮箱</label>
        <InputText @bind-Value="@loginModel.Email" class="form-control" />
        <ValidationMessage For="@(() => loginModel.Email)" />
    </div>

    <div class="mb-3">
        <label class="form-label">密码</label>
        <InputText type="password" @bind-Value="@loginModel.Password" class="form-control" />
        <ValidationMessage For="@(() => loginModel.Password)" />
    </div>

    <button type="submit" class="btn btn-primary">登录</button>
</EditForm>

@code {
    private LoginModel loginModel = new();
    [Inject] private SignInManager<ApplicationUser> SignInManager { get; set; }
    [Inject] private NavigationManager NavigationManager { get; set; }

    private async Task HandleLogin()
    {
        var result = await SignInManager.PasswordSignInAsync(
            loginModel.Email, 
            loginModel.Password, 
            loginModel.RememberMe, 
            lockoutOnFailure: false);

        if (result.Succeeded)
        {
            NavigationManager.NavigateTo("/");
        }
        else
        {
            // 处理登录失败（如提示错误信息）
        }
    }

    public class LoginModel
    {
        [Required]
        [EmailAddress]
        public string Email { get; set; } = string.Empty;

        [Required]
        [DataType(DataType.Password)]
        public string Password { get; set; } = string.Empty;

        [Display(Name = "记住我")]
        public bool RememberMe { get; set; }
    }
}

5. 调整用户注册逻辑 #

注册时直接将邮箱赋值给用户的Id和UserName：

private async Task HandleRegister()
{
    var user = new ApplicationUser { Email = registerModel.Email, UserName = registerModel.Email };
    var result = await UserManager.CreateAsync(user, registerModel.Password);

    if (result.Succeeded)
    {
        await SignInManager.SignInAsync(user, isPersistent: false);
        NavigationManager.NavigateTo("/");
    }
    else
    {
        // 处理注册失败逻辑
    }
}

6. 数据库迁移与更新 #

执行以下命令完成数据库结构更新：

Add-Migration ChangeUserIdToEmail
Update-Database

注意事项 #

• 若为现有项目，需先处理存量用户数据，确保所有用户邮箱唯一，并将Id字段更新为对应邮箱
• 所有依赖默认IdentityUser的业务代码（如角色关联、用户声明）需同步替换为ApplicationUser

内容的提问来源于stack exchange，提问作者LuisTheOne