调用SignInManager方法报错：Invalid Object name 'AspNetUserClaims'求助

问题原因 #

.NET Identity的SignInManager在登录流程中默认会尝试查询用户声明（Claims）数据，默认Identity实现依赖AspNetUserClaims表存储这类声明。即使你未手动添加用户声明，框架内部逻辑仍会尝试访问该表，导致表不存在时抛出异常。

解决方案 #

1. 自定义DbContext，移除不需要的Identity表映射 #

创建自定义DbContext，继承IdentityDbContext并移除声明、登录记录等无关DbSet及表映射：

public class AppDbContext : IdentityDbContext<AppUser, AppRole, string>
{
    public AppDbContext(DbContextOptions<AppDbContext> options) : base(options)
    {
    }

    // 移除默认的声明、登录、令牌相关DbSet
    public override DbSet<IdentityUserClaim<string>> UserClaims => null;
    public override DbSet<IdentityUserLogin<string>> UserLogins => null;
    public override DbSet<IdentityUserToken<string>> UserTokens => null;
    public override DbSet<IdentityRoleClaim<string>> RoleClaims => null;

    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        base.OnModelCreating(modelBuilder);
        
        // 取消这些表的EF Core映射
        modelBuilder.Entity<IdentityUserClaim<string>>().ToTable(null);
        modelBuilder.Entity<IdentityUserLogin<string>>().ToTable(null);
        modelBuilder.Entity<IdentityUserToken<string>>().ToTable(null);
        modelBuilder.Entity<IdentityRoleClaim<string>>().ToTable(null);
    }
}

2. 自定义UserManager，跳过声明查询 #

重写UserManager的GetClaimsAsync方法，直接返回空列表，避免访问AspNetUserClaims表：

public class CustomUserManager : UserManager<AppUser>
{
    public CustomUserManager(
        IUserStore<AppUser> store,
        IOptions<IdentityOptions> optionsAccessor,
        IPasswordHasher<AppUser> passwordHasher,
        IEnumerable<IUserValidator<AppUser>> userValidators,
        IEnumerable<IPasswordValidator<AppUser>> passwordValidators,
        ILookupNormalizer keyNormalizer,
        IdentityErrorDescriber errors,
        IServiceProvider services,
        ILogger<UserManager<AppUser>> logger) 
        : base(store, optionsAccessor, passwordHasher, userValidators, passwordValidators, keyNormalizer, errors, services, logger)
    {
    }

    public override Task<IList<Claim>> GetClaimsAsync(AppUser user)
    {
        // 返回空声明列表，不查询数据库
        return Task.FromResult<IList<Claim>>(new List<Claim>());
    }
}

3. 配置Identity服务，替换自定义组件 #

在Program.cs中配置Identity时，使用自定义的UserManager和DbContext：

builder.Services.AddIdentity<AppUser, AppRole>(options =>
{
    // 根据需求配置Identity选项（如密码规则、锁定规则等）
})
.AddEntityFrameworkStores<AppDbContext>()
.AddSignInManager<SignInManager<AppUser>>()
.AddScoped<UserManager<AppUser>, CustomUserManager>();

4. （可选）自定义ClaimsPrincipalFactory添加基础声明 #

如果需要为用户添加用户名、ID等基础声明但不想依赖AspNetUserClaims表，可自定义ClaimsPrincipalFactory：

public class CustomClaimsPrincipalFactory : UserClaimsPrincipalFactory<AppUser, AppRole>
{
    public CustomClaimsPrincipalFactory(
        UserManager<AppUser> userManager,
        RoleManager<AppRole> roleManager,
        IOptions<IdentityOptions> optionsAccessor) 
        : base(userManager, roleManager, optionsAccessor)
    {
    }

    protected override async Task<ClaimsIdentity> GenerateClaimsAsync(AppUser user)
    {
        var identity = await base.GenerateClaimsAsync(user);
        // 添加自定义基础声明
        identity.AddClaim(new Claim(ClaimTypes.NameIdentifier, user.Id));
        identity.AddClaim(new Claim(ClaimTypes.Name, user.UserName));
        return identity;
    }
}

注册该工厂：

builder.Services.AddScoped<IUserClaimsPrincipalFactory<AppUser>, CustomClaimsPrincipalFactory>();

验证 #

完成配置后重启应用，调用SignInManager的方法（如PasswordSignInAsync）时，将不再尝试访问AspNetUserClaims表，异常即可解决。

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