Sharing common database between .Net core and .Net standard Identity framework-CodePudding

The

CodePudding user response：

I faced the same problem and ended up creating new identity core tables using a schema.

builder.ToTable(name: "Users", "Identity"); builder.ToTable(name: "Roles", "Identity"); builder.ToTable(name: "UserRoles", "Identity"); builder.ToTable(name: "UserClaims", "Identity"); builder.ToTable(name: "UserLogins", "Identity"); builder.ToTable(name: "UserTokens", "Identity"); builder.ToTable(name: "RoleClaims", "Identity");

Then I used a trigger on the old identity users table to keep the new identity users table in sync.

CREATE/*ALTER*/ TRIGGER [dbo].[IdentityUsers_Sync] ON [dbo].[Users] AFTER INSERT, UPDATE AS BEGIN --INSERT IF NOT EXISTS (SELECT * FROM deleted) BEGIN INSERT INTO [Identity].[Users] ( Id, UserName, NormalizedUserName, Email, NormalizedEmail, EmailConfirmed, PasswordHash, SecurityStamp, PhoneNumber, PhoneNumberConfirmed, TwoFactorEnabled, LockoutEnabled, AccessFailedCount ) SELECT Id, UserName, UPPER(UserName), Email, UPPER(Email), EmailConfirmed, PasswordHash, SecurityStamp, PhoneNumber, PhoneNumberConfirmed, TwoFactorEnabled, 0, 0 FROM inserted END --UPDATE IF EXISTS (SELECT * FROM inserted) AND EXISTS (SELECT * FROM deleted) BEGIN UPDATE iu SET iu.UserName = i.UserName, iu.NormalizedUserName = UPPER(i.UserName), iu.Email = i.Email, iu.NormalizedEmail = UPPER(i.Email), iu.EmailConfirmed = i.EmailConfirmed, iu.PasswordHash = i.PasswordHash, iu.SecurityStamp = i.SecurityStamp, iu.PhoneNumber = i.PhoneNumber, iu.PhoneNumberConfirmed = i.PhoneNumberConfirmed, iu.TwoFactorEnabled = i.TwoFactorEnabled, iu.LockoutEnabled = 0, iu.AccessFailedCount = 0 FROM [Identity].[Users] iu, inserted i WHERE iu.Id = i.Id END END GO ALTER TABLE [dbo].[Users] ENABLE TRIGGER [IdentityUsers_Sync] GO

And my plan is to create an api controller in the legacy system to handle new registrations (via HttpClient in any new Core apps). Then the trigger will pick it up and keep the new system in sync.

Having the legacy system use the new identity tables doesn't look like an option at this point. Maybe additional fields could be added to the new schema and use a trigger to fill them in? Haven't tried that.

CodePudding user response：

recently I migrate a project from .net framework 4.6.1 to .Net 6 and I had this problem same as you. in my project I had a huge number of users so I decided to do this migration without breaking changes. based on this documentation: https://docs.microsoft.com/en-us/aspnet/core/security/authentication/identity-custom-storage-providers?view=aspnetcore-6.0

I used my User Store and Role Store in the project.

I add IdentityUser class as below :

public class IdentityUser<TKey> { /// <summary> /// Default constructor /// </summary> public IdentityUser() { } /// <summary> /// Constructor that takes user name as argument /// </summary> /// <param name="userName"></param> public IdentityUser(string userName) : this() { UserName = userName; } public IdentityUser(TKey id, string userName) : this(userName) { Id = id; } /// <summary> /// User ID /// </summary> public TKey Id { get; set; } /// <summary> /// User's name /// </summary> public string UserName { get; set; } /// <summary> /// Email /// </summary> public virtual string Email { get; set; } /// <summary> /// True if the email is confirmed, default is false /// </summary> public virtual bool EmailConfirmed { get; set; } /// <summary> /// The salted/hashed form of the user password /// </summary> public virtual string PasswordHash { get; set; } /// <summary> /// A random value that should change whenever a users credentials have changed (password changed, login removed) /// </summary> public virtual string SecurityStamp { get; set; } /// <summary> /// PhoneNumber for the user /// </summary> public virtual string PhoneNumber { get; set; } /// <summary> /// True if the phone number is confirmed, default is false /// </summary> public virtual bool PhoneNumberConfirmed { get; set; } /// <summary> /// Is two factor enabled for the user /// </summary> public virtual bool TwoFactorEnabled { get; set; } /// <summary> /// DateTime in UTC when lockout ends, any time in the past is considered not locked out. /// </summary> public virtual DateTime? LockoutEndDateUtc { get; set; } /// <summary> /// Is lockout enabled for this user /// </summary> public virtual bool LockoutEnabled { get; set; } /// <summary> /// Used to record failures for the purposes of lockout /// </summary> public virtual int AccessFailedCount { get; set; } } public class IdentityUser : IdentityUser<string> { public IdentityUser() { Id = Guid.NewGuid().ToString(); } public IdentityUser(string name) : base(name) { Id = Guid.NewGuid().ToString(); } public IdentityUser(string id, string name) : base(id, name) { } }

and here is my IdentityRole

public class IdentityRole : Microsoft.AspNetCore.Identity.IdentityRole<string> { public IdentityRole() { Id = Guid.NewGuid().ToString(); } public IdentityRole(string name) : base(name) { } } [Table("AspNetUsers", Schema = "someSchema")] public class ApplicationUser : IdentityUser { } [Table("AspNetRoles", Schema = "someSchema")] public class ApplicationRole : IdentityRole { } [Table("AspNetUserClaims", Schema = "someSchema")] public class ApplicationUserClaim : Microsoft.AspNetCore.Identity.IdentityUserClaim<int> { }

You have to implement the role store and user store based on your usage and after that you can use it in program.cs file

public class UserStore : IUserStore<ApplicationUser>, IUserClaimStore<ApplicationUser>, IUserLoginStore<ApplicationUser>, IUserRoleStore<ApplicationUser>, IUserPasswordStore<ApplicationUser>, IUserSecurityStampStore<ApplicationUser>, IUserEmailStore<ApplicationUser> { // interface implementations not shown }

and in the end add your UserStore and RoleStore in Program.cs

builder.Services.AddTransient<IUserStore<ApplicationUser>, UserStore>(); builder.Services.AddTransient<IRoleStore<ApplicationRole>, RoleStore<ApplicationUser, ApplicationRole>>();