HttpContext.Current.User and System.Threading.CurrentPrincipal

What is the difference between HttpContext.Current.User and System.Threading.CurrentPrincipal for an aspx page on a Windows 7 IIS running with Windows Authentication? What are the situations when these two will be different.

Thanks.

Re: HttpContext.Current.User and System.Threading.CurrentPrincipal

None in theory. For .NET, Thread.CurrentPrincipal is always the "goto" place to find out who the current user is. When ASP.NET was developed they wanted a slightly more convenient place to access this information, so they made HttpContext.User (and yes, it is redundant). So they're always supposed to be in sync.

If you ever write any code to assign either of these, then you should set both. An example of this would be assiging roles for a user in Application_PostAuthenticateRequest. If you mess that up, then that's the scenario where these would not be the same value and I would consider that a bug.