Professional Special Edition- P24:Those of us who are Microsoft developers can't help but notice that .NET has received a fair amount of visibility over the last year or so. This is quite surprising considering that for most of this period, .NET has been in its early infancy and beta versions. I can't remember any unreleased product that has caused this much interest among developers. And that's really an important point, because ignoring all the hype and press, .NET really is a product for developers, providing a great foundation for building all types of applications | Although the compilation settings allow us to control how the application is compiled they do not allow us to control how the application is run. To control the identity of the process that uses for compiling processing and servicing requests of our application we have the identity settings. Controlling the Identity of Execution We can use the identity setting of note that identity can be set in files as well to define which Windows user to impersonate when making requests from the operating system. This is separate from the trust level assigned to a particular application. The trust level set in the configuration system for an application determines what a particular application may or may not do. Trust levels are used to sandbox applications. We have three attributes used with identity impersonate - The impersonate attribute of identity is a Boolean value that determines the Windows NT user the worker process runs under. If impersonate true will run under the identity provided by IIS. If set to true this would be IUSR server name or whatever identity that IIS is configured to impersonate. However if Windows NT authentication is enabled on the web server will impersonate the authenticated user. Alternatively we can name a Windows NT user and password for the process to run as. The default setting of impersonate is False. userName - Available when impersonate true the name value names a valid Windows NT account to impersonate. password - Complementary to name the password of the user to impersonate. As mentioned above the default setting is impersonate false . Let s look at some examples where runs with impersonate true allowing the impersonation to flow from IIS as well as configuring the user password for to run as. Impersonating the IIS User To impersonate the user that IIS uses we first need to set impersonate true configuration identity impersonate true .
