Last post May 27, 2015 07:43 AM by Zhi Lv - MSFT
May 26, 2015 01:24 AM|bigolevy|LINK
We have a web site still running in Classic ASP and has it's own authentication mechanism.
We are building a new web site in MVC 5 C# and planning on using EF, and the ASP.NET Membership and Identity for authentication and authorization.
As an intermediary step we are planning to move all the users to use the new ASP.NET Identity for authentication. We will need to allow users that are visiting our old site (Still running in classic ASP) to be able to authenticate against the new site.
We are thinking of using the Identity via Web API calls, so a user visiting the Classic ASP site, will submit a username and password, the Classic ASP server will make a server side web service call to the Web Api for Authentication.
Would you do it any differently?
Thanks in advance.
May 27, 2015 07:43 AM|Zhi Lv - MSFT|LINK
From my point of view, I agree with you, you coud use Web API. Here are some relevant articles, please refer to them:
#Secure a Web API with Individual Accounts and Local Login in ASP.NET Web API 2.2
#External Authentication Services with ASP.NET Web API
#ASP.NET Web API