Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When user is connecting to my webservice I will set the Thread.CurrentPrincipal(messageinspector) with my custom context and this can then be used thou out the entire solution.
The question is if this Thread.CurrentPrincipal needs to be set to null or is this only living during the current call?
It does seem to only last for the current call but Im not sure if that just a coincident?
BestRegards
This property represents your current security login and therefore should probably not be set to null unless you have a particular need to do so. There are a number of situations where that would be appropriate (online banking, for example), but otherwise you will probably need it to continue accessing the resources you need to access.
Further reading at the MSDN article: http://msdn.microsoft.com/en-us/library/system.threading.thread.currentprincipal.aspx