title: How to secure an ASP.NET Core MVC client with a separate Core API?
body: <p>Currently, I have two clients for the same API, a Xamarin Forms app and an ASP.NET Core MVC project. Instead of using Entity in the MVC project and have to rewrite much of what has already been written in the API, we've decided to use the same API for both (isolating the database in the process).</p>
  
  <p>However, I've been having trouble trying to adapt Identity to this situation. Basically, we need to ask for login info in this MVC client, and then use the separate API to access the server and authenticate this info.</p>
  
  <p>There seems to be a few different ways to go about this, though I haven't yet been able to decide upon one/make one work as there isn't much documentation covering this specific scenario.</p>
  
  <p>Ideally, we'd like to be able to use the [Authorize] and other useful tags from Identity in this client MVC project, but haven't found a way to introduce our own API in this process. Any ideas?</p>