Re: Impersonation in ASP.NET 2.0 (works from XP, not 2003)
- From: "Adam Clauss" <cabadam@xxxxxxxx>
- Date: Wed, 22 Mar 2006 14:14:58 -0600
"Dominick Baier [DevelopMentor]" <dbaier@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:4580be63198a9e8c81c082f640e3f@xxxxxxxxxxxxxxxxxxxxx
In 2.0 - and i am pretty sure thats it is absolutely the same in 1.1 - the
<identity> element with explicit credentials causes the ISAPI to call
LogonUser - but LogonUser requires a password - so i am not sure why this
should work without supplying a password.
It would be a much better alternative to use app pools in IIS6. And they
run under NETWORK service by default.
Hmm... well, our goal was to have just one web.config file that worked on
either XP or 2003 - and in .NET 1.1 it worked fine. Now we have to remove
that line from the config file when running under 2003. It is still
required on XP (IIS5.1).
--
Adam Clauss
.
- Follow-Ups:
- Re: Impersonation in ASP.NET 2.0 (works from XP, not 2003)
- From: Adam Clauss
- Re: Impersonation in ASP.NET 2.0 (works from XP, not 2003)
- References:
- Impersonation in ASP.NET 2.0 (works from XP, not 2003)
- From: Adam Clauss
- Re: Impersonation in ASP.NET 2.0 (works from XP, not 2003)
- From: Dominick Baier [DevelopMentor]
- Impersonation in ASP.NET 2.0 (works from XP, not 2003)
- Prev by Date: RE: Best way to provide security when need a WindowsIdentity
- Next by Date: Re: ActiveDirectoryMembershipProvider - IsInRole problem
- Previous by thread: Re: Impersonation in ASP.NET 2.0 (works from XP, not 2003)
- Next by thread: Re: Impersonation in ASP.NET 2.0 (works from XP, not 2003)
- Index(es):