title: MVC6 Identity3 - How to create common User Accounts for multiple WebApps
body: <p>I'm new to MVC and currently working with MVC6 (EF7, Identity3, VS2015)...</p>
  
  <p>I would like create two different/independent WebApps in one company domain (in different sub domains).</p>
  
  <p>I would like use common/shared identity/login system for both Apps - in different words I would allow user to have one account across both Apps.</p>
  
  <p><em>I do not have option for domain authentication (the company doesn't use the domain - I know it's weird), so I must? use Individual User Accounts...</em></p>
  
  <p><strong>What is the best way/practice to create and use common user account across multiple apps ?</strong></p>
  
  <p>In first place I thought about creating two different DBContext in both App: one for Identity (Users DB) and second for App-Related Db...</p>
  
  <p>Such an approach would give me three different databases:</p>
  
  <ul>
  <li>IdentityDb - common for both WebApps,</li>
  <li>App1Db</li>
  <li>App2Db</li>
  </ul>
  
  <p>However I have doubts if it's good practice and the best way ?</p>
  
  <p>Probably will be enough one DBContext with proper configuration, but I don't have idea where I should start.</p>
  
  <p>I have read about SSO (Single Sign On) - but as far I understand it's about Authentication process, so it's little bit later - so I'm not sure about this direction.</p>
  
  <p>Anyway can't find example how to create common user account/profile across multiple apps.</p>
  
  <p><br>
  <strong>UPDATE:</strong></p>
  
  <p>My original question is probably too open... I would like ask not only 'what to do' but also 'how to do in MVC6'...</p>
  
  <p><strong>So my additional question is: how can I achieve this in MVC6? What I have to do? Perhaps some example?</strong></p>
  
  <p>If I decide for a separate User DB - then from the point of view of the application I will have two DB? What to do with this in code? Should I create two separate DBContexts - or just one?</p>
  
  <p>Also I have read few opinion here on SO, that using only one DbContext is better and simpler option...</p>
  
  <p>Anyway I have try yesterday works with 2x DBContext - everything works when I create new controller for IdentityDbContext, but I have error when trying create any controller for second DBContext (not associated with Identity)...</p>
  
  <p><em>(I've put description of this error to new question: <a href="https://stackoverflow.com/q/36407238/6131935">MVC6 Working with two DBContexts and error when create new controller</a>)</em></p>
  
  <p><br>
  <strong>Thanks in advance for any advice :)</strong></p>