ClaimsAuthenticationManager vs. IAuthenticationFilter vs. OWIN Forms Authentication

Viewed 2599

.NET 4.5, MVC 5: ClaimsAuthenticationManager, IAuthenticationFilter, OWIN Forms Authentication, and ClaimsPrincipals are all new since I last touched my site's authentication functions. I've found a lack of clarity in all the docs that say this or that is the right way. I can't even tell which features are mutually exclusive.

This document says the old ASP.NET FormsAuthenticationModule doesn't support Claims, but the new OWIN doesn't support cookieless. Yet, I get the feeling that OWIN is intended to be the go-forward feature?

  1. Does the product roadmap say which method is the go-forward for web-apps?
  2. Is ClaimsAuthenticationManager synonymous with OWIN Forms Authentication for web apps?
  3. Are the ClaimsAuthenticationManager and a global IAuthenticationFilter mutually exclusive?

A push in the right direction would be appreciated, my brain is fried on this.

2 Answers
Related