RE: <identity impersonate="true"/> means can, not is

Hello Dave,

As for the <identity impersonate="xxx" /> setting, when you set it to
"true", that means the ASP.NET runtime (of that application) will
automatically impersonate each worker thread to running under the security
context forwarded from IIS(the security context maybe a client
authenticated user or the IIS anonymous user). And this is done
automatically at the initializing time of the worker thread. So if you
do not want this to happen automatically, but want to do it yourself
programmatically, you should turn off this setting.

Hope this helps.

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

.

Relevant Pages

  • RE: Accessing remote perfmon/PDH data from a service, how to
    ... If the service is attempting to access a remote system with LocalSystem ... The security context for the ... The service account will need rights to access the target resource just as ...
    (microsoft.public.win2000.security)
  • Re: listing Object properties from SearchResult
    ... security context you bound with only has rights to see a subset of the ... > properties of all the object entries in a SearchResult but the code is ... > TIA ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: ATL Service and kernal object
    ... The MFC client is probably running in the security context different from ... rights of the event's security descriptor ... CDacl dacl; ... CSecurityDesc sd; ...
    (microsoft.public.vc.atl)