So, I am using ASP.NET Core Identity for the first time. I want to have one context for my login. I want another context for business objects. Where I am struggling is if I do this, I have the problem of users. I cannot use navigation properties to join business objects with a user under this strategy.
Initial thoughts are that I am going to have a user table separate from the AspNetUsers table in order to be able to do these joins. This means that somehow in my business logic, I need to populate this User table on creation of a record in AspNetUsers.
How have others handled this? Am I on the wrong track altogether here? Any guidance would be appreciated.