Click here to Skip to main content
13,351,457 members (47,468 online)
Click here to Skip to main content
Add your own
alternative version


23 bookmarked
Posted 27 Jan 2004

Securely Run the ASP.NET Worker Process as the System Account

, 27 Jan 2004
Rate this:
Please Sign up or sign in to vote.
Describes the proper way to configure a server to securely run the ASP.NET worker process runs as the system account.


There are several articles in existence about safely running the aspnet_wp.exe as the ASPNET user, or any other custom user that is specified in the <processModel> section of the machine.config file. However, when I attempted to run the ASP.NET worker process as "machine", or any other user that had the necessary permissions, I was unable to do so. After countless hours of creating a user, granting permissions, and following the steps set fourth by Microsoft in their patterns and practices document, what I found was that the effective settings in our Active Directory group policy were overriding the local policy that I set on my machine. While I'm sure that their directions were well and good for traditional settings, they covered nothing about being in Active Directory and what happens to the local user permissions once they are set.

However, there is a workaround for this dilemma. In the <processModel> element of the machine.config file, set the user name to "system" and the password to "AutoGenerate". Create a local user on your machine. The user will need permission to access all the necessary resources (GAC, Temporary ASP.NET Files directory, etc.). The list of necessary permissions can be found at MSDN. Additionally, if you store any username/password information in the registry, or if you need to access any legacy COM objects in a separate place on the server, the user will need to have the necessary rights.

Now, in the machine.config file, locate the <identity> element. The default setting for the <identity> element is:

<identity impersonate="false" userName="" password=""/>

If you set the identity impersonation to true, but do not specify a user name and password, then the worker process attempts to access files as the IUSR_machinename account. Now, specify a user name and password in the <identity> element, such as:

<identity impersonate="true" userName="myLocalUser" password="myUserPassword"/>

In this setup, it is true that the ASP.NET worker process still runs as system, but when the worker process tries to access files on the server (either in the virtual directory, or in the Temporary ASP.NET Files directory for just-in-time compilation), it does so as the user specified in the <identity> element, not as the system user.


This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here


About the Author

David Coe
Web Developer
United States United States
No Biography provided

You may also be interested in...


Comments and Discussions

GeneralAsyncronous Pin
Hugo Hallman16-Oct-04 15:04
memberHugo Hallman16-Oct-04 15:04 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Terms of Use | Mobile
Web03 | 2.8.180111.1 | Last Updated 28 Jan 2004
Article Copyright 2004 by David Coe
Everything else Copyright © CodeProject, 1999-2018
Layout: fixed | fluid