AppDomain.SetThreadPrincipal vs. Thread.CurrentPrincipal

  • Thread starter Thread starter Pradeep
  • Start date Start date
P

Pradeep

All,

If i set the Thread.CurrentPrincipal am i setting the
Principal or on AppDomain? Could someone explain how these
calls are different?
If i want to store and hand over user information from the
http request to the webservice implementation. Where is
the best place to put it? should i store it on
Thread.CurrentPrincipal, AppDomain.SetThreadPrincipal or
ClientContext.SetData.

Thanks for your help.
Pradeep
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

MVC Web-API - token based authentication 2
Thread.CurrentPrincipal still returns GenericPrincipal 2
Thread.CurrentPrincipal 4
Attach Custom Principal to Thead on one form, not there on other f 2
Sharing objects between Web and console 1
use Thread.CurrentPrincipal instead of HttpContext.User in a web application? 1
WindowsPrincipal.IsInRole fails when there is Whitespace in role n 1
threading and Principal question - from Role-based security to declarative security. 4

Back
Top