Reply to thread

Message: [QUOTE="Slezak, post: 4271152"] I agree, I'd rather know the appropriate way to perform this. I have found a resource at [URL]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsent7/html/vxconImpersonation.asp[/URL] that mentions this, but doesn't give a direct answer or example: "Note Impersonation is local to a particular thread. When code changes threads, such as when using thread pooling, the new thread executes using the process identity by default. When impersonation is required on the new thread, your application should save the security token (WindowsIdentity.Token Property) from the original thread as part of the state for the completion thread." Even worse, this resource has some bad [URL]http://msdn.microsoft.com/msdnmag/issues/01/11/security/default.aspx[/URL] "However, impersonation in Windows was designed for use in trusted server processes. If you make a call out to a random DLL, expecting it to run with only the privileges afforded to IUSR_MACHINE, you may get a big surprise. There is nothing stopping that DLL from simply removing the thread token by calling RevertToSelf and running in the security context of the process." I'd still love to hear from someone that could explain passing authentication to a child thread. Brian [/QUOTE]