aspnet local password

[BSleek]

How do I find the aspnet local password when my machine.config is set
to AutoGenerate? I need to login to my local host as this user. Thanks
for your help.

 

[Mary Chipman]

You can set the asp.net process identity by configuring a domain\user
account and password in the machine.config file. v1.1 lets you store
the password in an encrypted format. See
ms-help://MS.VSCC.2003/MS.MSDNQTR.2003OCT.1033/vsent7/html/vxconApplicationIdentity.htm
for more info.

--mary

 

[Ben Sleek]

Thanks for the reply, but is their a way this can be done without
changing the machine.config? I have other web applications using the
current setting, and would rather not change the default value.

 

[Mary Chipman]

Not that I know of, no. Why do you need to use this particular
account? Is there another Windows account that you can log on as to do
whatever it is you need to do?

--mary

 

[BSleek]

The reason I need to do this is because when I'm spawning a batch
process from the aspnet batch process, the process always defaults to
the local aspnet account. This is STILL the case even when I try to
impersonate an identity. Impersonation can run as a different users
from the ASP.NET context, but as soon as I try to call a windows batch
process it wants to run as local ASPNET user. If i could figure out
how to run my batch as a different user that would be a solution as
well, because I would already have knowledge of that user's password.
Thanks so much for your help.

 

[George Ter-Saakov]

Can you use API
CreateProcessWithLogonW

George

 

[Mary Chipman]

Unless George's solution works, I think you're going to have a problem
with this. the aspnet account is deliberately sandboxed so that it
can't be used in attacks against Windows, and allowing an unmanaged
batch process to run would constitute a serious security hole. Even if
the user had permissions to run the batch file, the fact that it's
being called from aspnet means that all callers in the stack do not
have the necessary permissions. You could probably loosen security
policy so that it worked, but then that would leave you vulnerable.

--Mary

 

[abeautifulmind]

*The reason I need to do this is because when I'm spawning a batch
process from the aspnet batch process, the process always default
to
the local aspnet account. This is STILL the case even when I try to
impersonate an identity. Impersonation can run as a different users
from the ASP.NET context, but as soon as I try to call a window
batch
process it wants to run as local ASPNET user. If i could figure out
how to run my batch as a different user that would be a solution as
well, because I would already have knowledge of that user'
password.
Thanks so much for your help. *

Not sure if this ever worked out for you, but here is a tool that list
the password of ASPNET user in your m/c. Run it from DOS

http://www.nirsoft.net/utils/anup.html[/url - abeautifulmin