Re: Permissions

From: Alvin Bruney [MVP] (vapor)
Date: 01/19/05 

Date: Tue, 18 Jan 2005 20:12:35 -0400

It's good that this is being addressed for 2.0. 

-- 
Regards,
Alvin Bruney
Coming this month
The Microsoft Office Web Components Black Book with .NET
http://tinyurl.com/27***
"Willy Denoyette [MVP]" <willy.denoyette@pandora.be> wrote in message 
news:Ok%234TmZ$EHA.2700@TK2MSFTNGP14.phx.gbl...
>
> "Alvin Bruney [MVP]" <vapor at steaming post office> wrote in message 
> news:eddOuWZ$EHA.3908@TK2MSFTNGP12.phx.gbl...
>>> Processes spawned that way inherit the process identity of the parent 
>>> process, never the identity of the thread that spawned the process.
>> Ok. But the parent was set to impersonate from the web.config file and 
>> not thru code impersonation, so the account (parent of the thread)should 
>> have been set to the impersonated account right? Or are you
>> saying that even with impersonation, the account was the asp.net account. 
>> I know this to be incorrect because a display of the principle showed the 
>> impersonated account for the main app.
>>
>> Somehow, the thread must have defaulted back to the aspnet account and 
>> not the impersonated account. There was no asp.net account on the NAS 
>> server where the file was to be written by the way but  the impersonated 
>> account existed.
>> Could this be a bug?
>>
> No, it's not a bug.
> Your asp worker process identity is taken from the web.config file 
> <processmodel element - userName and password attributes.
> Impersonation only indicates what thread identity should be taken for an 
> unauthenticated client when impersonating, but as I said before the 
> process identity is used when spawning another process.
>
> Willy.
>
>
>
>