views:

10

answers:

0

I'm trying to debug a file permission problem. I'm running ASP.NET 2.0 on Windows 2003 32-bit standard edition.

ASP.NET 2.0 is configured to impersonate my web sites anonymous accounts. In my machine.config file (in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG) I have:

<identity impersonate="true" />

I know that ASP.NET requests are being impersonated because I have a test page that does this:

<%@ Page Language="C#" %>
<%@ Import Namespace="System.Security.Principal" %>
<script runat="server">
    void Page_Load(Object sender, EventArgs e)
    {
        Response.Write(WindowsIdentity.GetCurrent().Name);
    }    
</script>

This page correctly displays the site's IIS anonymous identity (<MACHINENAME>\I_testsite).

Additionally the site is locked down using NTFS permissions so that only the anonymous account can create & write files (Modify permission) which works fine using a simple test script (I'm debugging an issue for a customer with Cute-Editor where I think it's misconfigured).

The worker process account only has read access (required so that ASP.NET can monitor for file changes to trigger recompiles of the site in the shadow copy folders).

When I run Process Monitor I never see the impersonated anonymous account accessing files. I only ever see the worker process account accessing files in the web folders.

The only filter I'm using in ProcMon is to monitor access where the path contains d:\websites\mysite\www which is the root of my site.

Why is this? I'm sure process monitor used to show the impersonated account in previous versions?