Difference between FormsAuthentication Microst.AspNet.Identity.Owin.SignInManager.to authenticate

Question

The default Project template of ASP.NET MVC comes with a class named Microst.AspNet.Identity.Owin.SignInManager. This class is used to authenticate users

I dont understa

Answer 1

The Idea is for OWIN to be Platform Agnostic. It's "Middleware" between your ASP.NET application and the platform that is running it. Forms Authentication is built for ASP.NET on IIS. OWIN can use other providers such as Google and Facebook.

Have a look at this article : https://www.tektutorialshub.com/owin/introduction-to-owin/

Answer 2

MembershipProvider came with FormsAuthentication in ASP.NET 2.

ASP.NET Identity came with SignInManager in ASP.NET 5.

ASP.NET Identity is a new version of MembershipProvider. It offers a lot more features than legacy MembershipProvider.

For example,

• Two-factor authentication
• Token-based authentication
• Easy-to-add custom properties compare to MembershipProvider
• Get instance of UserManager from the OWIN context

If you do not need all those features, you can stick with FormsAuthentication which can be used without MembershipProvider.

Answer 3

Forms Authentication is the old version of the authentication framework for ASP.NET. One really solid reason against using Forms authentication, is that it is deprecated.

The default template for ASP.NET MVC in the latest version of Visual Studio has an implementation of ASP.NET Identity Framework, hence the use of SignInManager. I believe that one of the main advantages to using ASP.NET Identity this is that it is hostable as OWIN middleware, which means it has no reliance on System.Web and thus no reliance on your web application.