title: Use separate DB Context for Identity 2 and application models
body: <p>I am using VS.2017 with EF6 with ASP.NET Core template to create a website. I would like to know whether it is really possible to use two different Application DB contexts on my web application.</p>
  
  <p>Since it is the default template with Individual Accounts, it already comes with a standard migration to create the Identity 2 repository on the database. It also has the default ApplicationDBContext although I don't see any entity being exposed in the default ApplicationDBContext (should it not expose User?)</p>
  
  <p>I am sure many will ask WHY. I want to have the default application DB context (context 1) for Identity 2.x and then context 2 for my application's models so that I can separate them.</p>
  
  <p>The idea behind being that the Identity Context will be hosted in a separate database for Single Sign On but only modified to associate a user account with a specific web application site.</p>
  
  <p><strong>UPDATE 1</strong>
  As stated there will be multiple domains using the same "Identity Server" BUT I do not need to be able to use the same user to automatically login to the other site. In other words, the Identity Server is a shared database to keep identity data but each domain is aware of its own users (and ignores uses of the other domains).</p>
  
  <p>For that reason the first DB context would be for the "Identity Server" database and teh second DB context for application models not related to identity.</p>