is there a way to run iisexpress app pool under a different identity other than the currently logged in user?
I am getting around this problem using the \"runas\" co
"runas" is only the solution. IIS Express maynot respect processModel settings which are defined in applicationhost.config file.
It looks like this should be possible. In your IIS Express site's applicationhost.config file, there is a <processModel/>
element defined in <applicationPoolDefaults>
under <applicationPools>
The <processModel>
element has attributes for userName
and password
.
From MSDN:
Specifies that ASP.NET will run the worker process with a Windows identity that is different from the Windows identity for the default process identity. By default, this attribute is set to the Machine, and the process runs under a user account named ASPNET that is created automatically when ASP.NET is installed. The password for the ASPNET account is cryptographically generated at the time of installation. If valid credentials are presented in this attribute and the password attribute, the process is run with the given account.
This should allow you to run the site under different credentials from the logged in user.
I wonder if this really works - IIS Express seems to run all application pools in the same process - and that process is executed in the context of the current user...?
Seems the "Run as" option could work, but that would require us to launch IIS Express from the command line (or build event) instead of relying on Visual Studio starting it up. :(
I could not get the above solution to work and I wanted to be able to debug through Visual Studio while running IIS Express under different credentials.
You can now debug as normal under IISExpress (assuming this is how you have your project configured) under the run as credentials. This is great if you need to use integrated security for database connections or something similar but need to use different credentials.
Runas /netonly IISExpress.exe from command line does work and is very viable if you're as desperate for an answer as we were. Related post