OWIN Cookies vs. FormsAuthentication

Question

Are there any significant benefits of using OWIN cookie authentication over cookie authentication based on authentication forms for developing MVC web applications?

The reason I'm asking is because I would not use any of the Entity Framework-based intercepts for OWIN authentication. I have been developing applications based on Autodesk Forms Authentication for many years and could do things such as creating various authentication tokens for administrators (faster timeouts), anonymous users, and registered users. Using the UserData part for the ticket, I was able to implement universal exit, save user properties, etc.

One of the benefits of OWIN can be testability, but I'm not sure. The ClaimsIdentity element is good because I can easily store and access custom fields without having to serialize / deserialize the properties in UserData. Other things I should consider?

Answer 1

Cookie intermediate authentication can run on any OWIN host, including IIS, while FormsAuthenticationModule can only work on IIS + ASP.NET. If you have a present or future need for hosting on different types of hosts, CAM is the best option. Another middleware tool, but not FAM, is cookies. If your user data is large enough for the cookie to exceed the size limit, the browsers simply stopped sending authentication cookies, while the middleware put large cookies on several small cookies and collects them upon receipt.