如何无需创建管理器访问Identity方法？自定义用户架构疑问

Hey Paul, great question—let’s walk through your options clearly so you can pick what works best for your setup.

You don’t have to adopt the full Identity architecture to use parts of UserManager. The key here is that UserManager relies on a set of abstractions (like IUserStore<TUser>, IUserPasswordStore<TUser>, etc.) instead of being tightly coupled to Identity’s built-in database context.

If you only need specific features (e.g., password hashing, user lookup, password validation), you can implement just the interfaces required for those features, not the entire suite. For example:

• If you want password-related methods (CreateAsync with password hashing, CheckPasswordAsync), implement IUserPasswordStore<TUser> alongside the base IUserStore<TUser>.
• If you need email confirmation, add IUserEmailStore<TUser>.

This approach lets you leverage UserManager’s battle-tested logic without buying into the full Identity schema or pipeline. You’ll just need to map your custom user model and database operations to these interfaces.

If even implementing minimal Identity interfaces feels overkill, you can extract and replicate only the UserManager functionality you need, using standalone Identity components where possible.

For example, the PasswordHasher<TUser> is a standalone class in Identity that you can use directly without the rest of the framework:

// Using PasswordHasher without full Identity
var passwordHasher = new PasswordHasher<CustomUser>();
var hashedPassword = passwordHasher.HashPassword(yourCustomUser, "userPassword123");
var verificationResult = passwordHasher.VerifyHashedPassword(yourCustomUser, hashedPassword, "userPassword123");

You can then wrap this (and your custom database operations) into your own lightweight CustomUserManager class that includes only the methods you need—like CreateUserAsync, GetUserByIdAsync, ValidateUserCredentialsAsync, etc. This gives you full control over the logic while avoiding any unnecessary Identity coupling.

• Go with Option 1 if your required features align closely with UserManager’s core capabilities (password management, user state tracking) and you want to reuse proven, secure code.
• Choose Option 2 if your user system has highly custom logic, or you want to keep your codebase completely decoupled from Identity’s abstractions.

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