[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

x
?
Solved

Web service thread doesn’t inherit security context

Posted on 2004-08-24
2
Medium Priority
?
336 Views
Last Modified: 2010-04-17
Using .NET 1.1 – Windows 2003.

I've created a web service that spawns a thread.  The service needs access to other servers, so I've created a user (lets call it "ServiceUser") with privileges and assigned the "anonymous user" in IIS to that user.  I then added <identity impersonate="true"/> to the web.config of my web service.

From inside any of the functions of the web service I make a call to WindowsIdentity.GetCurrent (which displays the current user), it returns "ServiceUser".  Great!  If I spawn a thread from that function and launch it, then I call WindowsIdentity.GetCurrent inside that spawned thread, it returns "ASPNET".

All I want is for the thread to have the same security context as it's calling function.  I've read solutions that require "ServiceUser" or ASPNET to have "Act as part of operating system" checked.  Anyone have a more elegant solution?

Thanks,
Chris
0
Comment
Question by:zebrachris
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 5

Accepted Solution

by:
Dragonmen earned 1500 total points
ID: 11890163
Thread that you are spawning is using an ASP.NET account becouse no other account is given to that thread.
Every thread has it's own security context.
Look @ this:
http://pluralsight.com/wiki/default.aspx/Keith.GuideBook.HowToImpersonateAUserGivenHerToken
0
 

Author Comment

by:zebrachris
ID: 11894112
Actually I've tried assigning the context to the thread directly.

   'create thread to handle processing
   Dim th_DORProcess = New Thread(AddressOf oImportObject.StartProcess_Thread)
   'Pass credentials
   th_DORProcess.CurrentPrincipal = New System.Security.Principal.WindowsPrincipal(System.Security.Principal.WindowsIdentity.GetCurrent)
   'start the thread executing
   th_DORProcess.Start()

I've walked through this code and verified that the windows identity I want is set to the current principle of the thread.  Once the thread is started though, it reverts to the ASPNET process.

I tried WindowsImpersonationContext as per Dragonmen's link above and it works great.  (Thanks Dragonmen)

..I am wondering though, why it works.  Microsoft themselves even says that it shouldn't in the comments of the WindowsImpersonationContext example code:

' This sample demonstrates the use of the WindowsIdentity class to impersonate a user.
' IMPORTANT NOTES:
' This sample can be run only on Windows XP.  The default Windows 2000 security policy
' prevents this sample from executing properly, and changing the policy to allow
' proper execution presents a security risk.




0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Today, the web development industry is booming, and many people consider it to be their vocation. The question you may be asking yourself is – how do I become a web developer?
What do responsible coders do? They don't take detrimental shortcuts. They do take reasonable security precautions, create important automation, implement sufficient logging, fix things they break, and care about users.
Introduction to Processes
Starting up a Project

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question