App pool identity versus impersonation identity? App pool identity versus impersonation identity? asp.net asp.net

App pool identity versus impersonation identity?


Using impersonation in the web.config allows you to override whatever identity was configured for the Application Pool the app is running under - it's just a more fine grained method to control identity ( on the app level vs. the ApplicationPool level), so you could have two apps run on the same AppPool, but one of them uses impersonation to use another identity.