Move the ApplicationUser definition to your DAL. Inherit your MyDbContext from IdentityDbContext<ApplicationUser> or IdentityDbContext OnModelCreating – Provide the foreign key info. Pass MyDbContext while creating the UserManager<ApplicationUser>
With the current aspnet core version (2.1.0), this has changed, now you can use the extensions: services.ConfigureApplicationCookie(options => options.LoginPath = “/login”); or services .AddAuthentication() .AddCookie(options => { options.LoginPath = “/login”; options.LogoutPath = “/logout”; }); You can see more about migrating in to 2.0 in this article.
Your code does’t show this, but from the errors you are getting I assume that you are overriding OnModelCreating.This is where IdentityDbContext<ApplicationUser> configure the entity framework mappings. This means that if you want to override OnModelCreating you need to either call the base or you must do the mapping yourself. So either this: protected override … Read more
You do have two DbSets` of the same type. IdentityDbContext<T> itself contains Users property declared as: public DbSet<T> Users { get; set; } You’re declaring second one in your class.
Update Dec 2017 Some good points have been raised in comments: Better have a separate field for new email while it is getting confirmed – in cases when user have entered incorrect email. Wait till the new email is confirmed, then make it the primary email. See very detailed answer from Chris_ below. Also there … Read more
The intent was to allow both arbitrary id types (i.e. int, guid, string), but also avoid having serialization/casting issues for the id property. So you can define your keys however you like and just implement the interface method public class MyUser : IUser { public int Id { get; set; } string IUser.Id { get … Read more
MOQ is good for mocking interfaces, but does not work so well with concrete classes. So instead of mocking concrete class, ask for the inteface: var userStore = new Mock<IUserStore<PreRegistrationMVC.Models.ApplicationUser>>(); Also ApplicationUser should be POCO, so no need to mock it, just create its instance without MOQ and use in tests.
In the MVC project template in VS2013 Update 2, there should be a file called App_Start/IdentityConfig.cs. In it you should find the class ApplicationUserManager and a static factory method called Create(). That’s where the user manager class is configured, including the server-side validation rules for passwords are defined. For example: manager.PasswordValidator = new PasswordValidator { … Read more
My way of doing this is to create a class in models namespace. public class SampleData { public static void Initialize(IServiceProvider serviceProvider) { var context = serviceProvider.GetService<ApplicationDbContext>(); string[] roles = new string[] { “Owner”, “Administrator”, “Manager”, “Editor”, “Buyer”, “Business”, “Seller”, “Subscriber” }; foreach (string role in roles) { var roleStore = new RoleStore<IdentityRole>(context); if (!context.Roles.Any(r … Read more
The correct place to add claims, assuming you are using the ASP.NET MVC 5 project template is in ApplicationUser.cs. Just search for Add custom user claims here. This will lead you to the GenerateUserIdentityAsync method. This is the method that is called when the ASP.NET Identity system has retrieved an ApplicationUser object and needs to … Read more