NTFS + Impersonation + Asp.Net
From: David Fanning (dfanning@europeancredit.com)
Date: 09/20/02
- Next message: Willy Denoyette [MVP]: "Re: NTFS + Impersonation + Asp.Net"
- Previous message: dirk diggler: "property access after Dispose()"
- Next in thread: Willy Denoyette [MVP]: "Re: NTFS + Impersonation + Asp.Net"
- Reply: Willy Denoyette [MVP]: "Re: NTFS + Impersonation + Asp.Net"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "David Fanning" <dfanning@europeancredit.com> Date: Fri, 20 Sep 2002 03:19:55 -0700
Ok, appologies I know Impersonation has been done to death
however I couldn't find much help about NTFS file
permissions and Asp.Net.
My problem is as follows;
I've deployed an Asp.Net app so it impersonates the user
logging in with a valid certificate (certificate mapping).
I'm pretty sure the impersonation is working correctly,
I've check both the User.Identity.Name and the more useful
System.Security.Principal.WindowsIdentity.GetCurrent
().Name and both appeared to reflect the correct NT
Account.
HOWEVER, as a test I set NTFS file permisions to refuse
access to a web page for this NT Account (TestUser). Guess
what, the web page was still shown.
What's going on here, I thought any 'Deny' NTFS
permissions take precendence over 'Grant'.
Are there any good resources that explains, preferably
with an example exactly how to setup NTFS file security
with an Asp.Net app executing under a specific 'User' NT
account.
Many Thanks
David
- Next message: Willy Denoyette [MVP]: "Re: NTFS + Impersonation + Asp.Net"
- Previous message: dirk diggler: "property access after Dispose()"
- Next in thread: Willy Denoyette [MVP]: "Re: NTFS + Impersonation + Asp.Net"
- Reply: Willy Denoyette [MVP]: "Re: NTFS + Impersonation + Asp.Net"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|