title: Thread.CurrentPrincipal is authenticated but ClaimsPrincipal.Current is not
body: <p>I'm using Claims based Authorization in my WebApi project and have a method where I check if the current Identity is authenticated. When I use <code>ClaimsPrincipal.Current</code> the current Identity is not authenticated but when I use <code>Thread.CurrentPrincipal</code> it is.</p>
  
  <pre><code>ClaimsPrincipal.Current.Identity.IsAuthenticated; //False
  Thread.CurrentPrincipal.Identity.IsAuthenticated; //True
  </code></pre>
  
  <p>This seems strange especially since the <a href="http://msdn.microsoft.com/en-us/library/system.security.claims.claimsprincipal.current.aspx" rel="noreferrer">MSDN says</a>  ClaimsPrincipal.Current just returns Thread.CurrentPrincipal:</p>
  
  <blockquote>
    <p><strong>Remarks</strong></p>
    
    <p>By default, Thread.CurrentPrincipal is returned. You can change this
    behavior by setting the ClaimsPrincipalSelector property to specify a
    delegate to be called to determine the current principal.</p>
  </blockquote>
  
  <p>Can someone please explain me why <code>ClaimsPrincipal</code> is not authenticated, while both, in theory, contain the same Identity?</p>