We currently have an Asp.Net MVC 5.0 project that utilizes AngularJS for the front end. The project includes a WebAPI Controller within the same project and is deployed on the same website. This application was created using the Individual User Account project template and incorporates Asp.Net Identity and Claims. One of the features is a file upload module where users can upload files over 100MB, which then go through the webapi and ng-file-upload plugin. Due to a growing user base, we are looking to enhance the upload speed by separating the API into its own site on a new server for scalability purposes. The current API controller operates under ASP.NET MVC solution with OWIN cookie authentication, allowing authorization through the cookie authentication middleware. What would be the most efficient way to move the API onto a separate site? It seems that implementing OAuth token based on the MVC site and configuring the new API site to consume this token via CORS may be necessary. However, whether we need to eliminate cookie-based authentication and replace it with token-based authentication remains unclear. Are there alternative approaches that would allow us to retain cookie-based authentication for the Asp.Net MVC site while relocating the API to a new site?
In addition, we are considering building a mobile app that will interact with this API, further emphasizing the need to separate the webapi into its own site and implement OAuth token-based authorization.
Thank you for your assistance!
Best regards, Bala