ASP.Net Impersonation
From: Mark Miller (mark_no_s_p_am__at_maxpreps.com)
Date: 12/30/04
- Previous message: Peter Afonin: "Re: Output folder changed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 30 Dec 2004 10:35:05 -0800
I am trying to understand Impersonation in the ASP.Net context. Here's what
I DO understand:
-Using Windows Authentication with impersonation="true" means that the
aspnet_wp will try and access the resource with the authenticated user's
credentials (token). If access is denied I get an IIS access denied message.
-I can set NTFS permissions on a file/folder and control access w/o using
code simply by assigning rights by user or group.
-setting impersonation="false" still authorizes the user using NTFS
permissions, but instead it is the aspnet_wp account that accesses the file
and checks the permissions. Then if access is denied ASP.Net throws an
exception.
Here's what I DON'T understand:
-What's the difference then between Windows Authentication with
impersonation turned on, and windows impersonation turned off? Other than
where the authorization takes place (ie. aspnet_wp or NTFS).
-When would I want to use one over the other?
Thanks in advance,
Mark Miller
- Previous message: Peter Afonin: "Re: Output folder changed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|