title: ClaimsAuthenticationManager vs. IAuthenticationFilter vs. OWIN Forms Authentication
body: <p>.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 <em>this</em> or <em>that</em> is the right way. I can't even tell which features are mutually exclusive.</p>
  
  <p><a href="http://blogs.msdn.com/b/webdev/archive/2013/07/03/understanding-owin-forms-authentication-in-mvc-5.aspx">This document</a> says the old ASP.NET <code>FormsAuthenticationModule</code> 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?</p>
  
  <ol>
  <li>Does the product roadmap say which method is the go-forward for web-apps?</li>
  <li>Is ClaimsAuthenticationManager synonymous with OWIN Forms Authentication for web apps?</li>
  <li>Are the ClaimsAuthenticationManager and a global IAuthenticationFilter mutually exclusive?</li>
  </ol>
  
  <p>A push in the right direction would be appreciated, my brain is fried on this.</p>