.NET 5 Clean Architecture下关联.NET Core Identity与UserProfile方案咨询

1. 领域层UserProfile调整 #

仅新增无业务含义的通用所有者标识字段，不需要任何Identity相关引用：

namespace Core.Domain
{
    public class UserProfile : AuditEntity
    {
        // 新增通用标识字段，仅为普通整数类型，领域层无需感知其关联Identity
        public int OwnerId { get; set; }

        // 原有属性保持不变
        [StringLength(50)]
        public string FirstName { get; set; }
        [StringLength(50)]
        public string LastName { get; set; }
        [StringLength(50)]
        public string JobPosition { get; set; }
        [StringLength(50)]
        public string Photo { get; set; }
        [DefaultValue(true)]
        public bool IsListed { get; set; }
        [DefaultValue(false)]
        public bool IsDisabled { get; set; }
        [DefaultValue(false)]
        public bool IsLocked { get; set; }
        public DateTime? LastLoginDate { get; set; }
        public DateTime? LastActivityDate { get; set; }
        [StringLength(100)]
        public string LastSessionId { get; set; }
        [StringLength(256)]
        public string PrivateFolder { get; set; }
        public bool IsOnApproval { get; set; } = true;
        public bool IsDeleted { get; set; } = false;
    }
}

2. 基础设施层配置关联规则 #

在Infrastructure层的EF实体配置中定义外键关联和级联操作，这部分逻辑完全隔离在基础设施层，对领域层透明：

// Infrastructure/Data/Configurations/UserProfileConfiguration.cs
using Core.Domain;
using Infrastructure.Identity;
using Microsoft.EntityFrameworkCore;
using Microsoft.EntityFrameworkCore.Metadata.Builders;

namespace Infrastructure.Data.Configurations
{
    public class UserProfileConfiguration : IEntityTypeConfiguration<UserProfile>
    {
        public void Configure(EntityTypeBuilder<UserProfile> builder)
        {
            // 配置与ApplicationUser的一对一关联
            builder.HasOne<ApplicationUser>()
                .WithOne()
                .HasForeignKey<UserProfile>(nameof(UserProfile.OwnerId))
                .IsRequired()
                // 配置级联删除，删除Identity用户时自动删除关联UserProfile
                .OnDelete(DeleteBehavior.Cascade);
        }
    }
}

同时在ApplicationDbContext中添加UserProfile的DbSet：

public DbSet<UserProfile> UserProfiles { get; set; }

原有OnModelCreating已经配置了自动加载当前程序集的配置，不需要额外修改。

3. 实现创建用户自动同步逻辑 #

在Application层定义通用身份服务接口，在Infrastructure层实现该接口，封装用户创建逻辑，保证同一事务内同时创建ApplicationUser和UserProfile：
首先在Application/Interface下新增IIdentityService.cs：

namespace Application.Common.Interfaces
{
    public interface IIdentityService
    {
        Task<(bool Succeeded, string UserId, string[] Errors)> CreateUserAsync(string email, string password, UserProfile profile);
        Task<(bool Succeeded, string[] Errors)> DeleteUserAsync(int userId);
    }
}

在Infrastructure层实现该接口：

// Infrastructure/Services/IdentityService.cs
using Application.Common.Interfaces;
using Core.Domain;
using Infrastructure.Identity;
using Microsoft.AspNetCore.Identity;
using Microsoft.EntityFrameworkCore;

namespace Infrastructure.Services
{
    public class IdentityService : IIdentityService
    {
        private readonly UserManager<ApplicationUser> _userManager;
        private readonly ApplicationDbContext _dbContext;

        public IdentityService(UserManager<ApplicationUser> userManager, ApplicationDbContext dbContext)
        {
            _userManager = userManager;
            _dbContext = dbContext;
        }

        public async Task<(bool Succeeded, string UserId, string[] Errors)> CreateUserAsync(string email, string password, UserProfile profile)
        {
            using var transaction = await _dbContext.Database.BeginTransactionAsync();
            try
            {
                var user = new ApplicationUser { UserName = email, Email = email };
                var createResult = await _userManager.CreateAsync(user, password);
                if (!createResult.Succeeded)
                {
                    return (false, null, createResult.Errors.Select(x => x.Description).ToArray());
                }

                profile.OwnerId = user.Id;
                _dbContext.UserProfiles.Add(profile);
                await _dbContext.SaveChangesAsync();

                await transaction.CommitAsync();
                return (true, user.Id.ToString(), Array.Empty<string>());
            }
            catch
            {
                await transaction.RollbackAsync();
                throw;
            }
        }

        public async Task<(bool Succeeded, string[] Errors)> DeleteUserAsync(int userId)
        {
            var user = await _userManager.FindByIdAsync(userId.ToString());
            if (user == null)
                return (false, new[] { "用户不存在" });

            // 因配置了级联删除，删除用户时自动删除关联UserProfile，无需手动操作
            var deleteResult = await _userManager.DeleteAsync(user);
            return (deleteResult.Succeeded, deleteResult.Errors.Select(x => x.Description).ToArray());
        }
    }
}

最后在DependencyInjection.cs中注册该服务：

services.AddScoped<IIdentityService, IdentityService>();

• 完全满足约束：领域层UserProfile无任何Identity相关依赖，ApplicationUser始终保留在Infrastructure层
• 自动同步无额外开发成本：删除操作通过数据库级联自动处理，创建操作通过事务封装保证一致性，不存在孤儿数据问题
• 无抽象漏洞：即便是直接调用UserManager的删除方法，EF Core级联规则也会自动触发UserProfile的删除，所有基于当前ApplicationDbContext的操作都会遵守关联规则
• 兼容扩展：后续新增的关联实体都可以用相同的方式配置关联，不需要修改上层逻辑

内容的提问来源于stack exchange，提问作者Hugo A.