Ahhh. I think this is a matter of the later OS being more secure. Code
access security is going to do a lot to prevent internet hosted logic from
doing things that require admin permissions. You want to think VERY
carefully about undoing this protection. Since .NET 1.1 was shipped as a
part of Windows Server 2003, I suspect that the policy expressions that
shipped with this version were more restrictive. If this is the case, no
amount of impersonation is going to fix this - since the call is
originating from a web service and thus is sand boxed. You'd have to
override code access security for these specific operations. I would still
add logic to such a service to make sure that the caller is a member of a
group the caller recognizes ad an admin, since once you over-ride the
sandbox security, no other protections would be keeping a non-admin from
making a call that if overdone could flood your box and disable your server.
I hope this helps
Dan
--------------------
>Thread-Topic: IIS Virtual Directory Create Failure :(
>thread-index: AcTMurvE7+6ff34BSxC8pHYgFuZQvQ==
>X-WBNR-Posting-Host: 63.162.177.130
>From: =?Utf-8?B?RXNraW1v?= <Eskimo@discussions.microsoft.com>
>References: <E288D499-3B3F-4B1D-BC17-D3F32A78249C@microsoft.com>
<BsZ7jyDzEHA.1184@cpmsftngxa10.phx.gbl>
>Subject: RE: IIS Virtual Directory Create Failure :(
>Date: Wed, 17 Nov 2004 07:33:05 -0800
[quoted text clipped - 13 lines]
>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:26666
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 109 lines]
>> >
>> >
deNewVDir.Properties["Path"].Insert(0,"c:\temp\Eskimo\");
>> >...
>> > deNewVDir.Properties["AccessRead"][0] =true;
[quoted text clipped - 19 lines]
>> >windows app test project and the web service accessing the DLL project.
>> >In a web service I get the error listed above... :(
Eskimo - 22 Nov 2004 16:57 GMT
Dan,
What can I do to "You'd have to override code access security for these
specific operations" ?
Where do I start with code access security? I did give fulltrust to the
assembly calling the IIS stuff with caspol -af <DLL ASSEMBLY> I was wanting
to use full trust with...
I have an n-tier application, with a set of objects that manipulate ADSI
with the .NET framework classes found in System.DirectoryServices.
> Ahhh. I think this is a matter of the later OS being more secure. Code
> access security is going to do a lot to prevent internet hosted logic from
[quoted text clipped - 185 lines]
> >> >windows app test project and the web service accessing the DLL project.
> >> >In a web service I get the error listed above... :(