current-principal

Would using Thread.CurrentPrincipal's claims in a referenced library that uses ConfigureAwait(false) pose any problems or will the flowing of ExecutionContext's logical call context take care of me there? (my reading and testing so far indicates that it will). Example WebAPI Controller Action: [CustomAuthorizeThatSetsCurrentUsersClaimsToThreadCurrentContextAndHttpContextCurrentUser] public async Task<Order> Get(int orderId) { return await _orderBusinessLogicLibrary.LoadAsync(orderId); // defaults to .ConfigureAwait(true) } Example load functions from external, referenced library:

Possible Duplicate: difference between http.context.user and thread.currentprincipal and when to use them? What's the difference between these two in an ASP.NET application? I know the HttpContext.User.Identity is set when the user is authenticated through FormsAuthentication . But when is the Thread.CurrentPrincipal.Identity set? Do they always hold the same value? Does that still hold true for other layers of the application that do not have access to a HttpContext ? HttpContext.User.Identity is the current logged in user in your web app. Thread.CurrentPrincipal applies only when the

I enabled impersonation and windows authentiaction. <authentication mode="Windows" /> <identity impersonate="true" userName="name" password="passord"/> But Thread.CurrentPrincipal.Identity.Name returnes the name of authenticated user and WindowsIdentity.GetCurrent() returns impersonated identity. Shouldn't these identities be the same? And under wich credentials does the code run in this case? Andrei Zubov As far as I can understand the Thread.CurrentPrincipal contains the information of conditions the thread has been started with, including the WindowsIdentity. That's why Thread