you are confusing two concepts with asp.net. authentication (how the
user is) and thread identity (impersonation).
authentication=windows inpersonate=true
is telling asp.net that the windows authenication was used, and to
impersonate the hosts identity.
you are coding it the same way as iis does. it impersonates the
webclient before accessing any resources (such as asp.net or the file
system).
-- bruce (sqlwork.com)
> Hi,
> I've developed in .net 2.0 a custom web server that hosts asp.net sites
[quoted text clipped - 14 lines]
>
> Thank you
Enrico Sabbadin - 18 Jul 2007 08:18 GMT
i'm not confusing the 2 concepts , i know the difference..
i'm just asking if authentication=windows inpersonate=true is something i
should take care in custom web hosting , or it's something out of the box if
i code properly
> you are confusing two concepts with asp.net. authentication (how the user
> is) and thread identity (impersonation).
[quoted text clipped - 27 lines]
>>
>> Thank you
Enrico Sabbadin - 18 Jul 2007 11:08 GMT
i found the solution here
http://www.leastprivilege.com/HttpListenerAuthenticationAndASPNET.aspx
> i'm not confusing the 2 concepts , i know the difference..
> i'm just asking if authentication=windows inpersonate=true is something i
[quoted text clipped - 33 lines]
>>>
>>> Thank you