Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > Impersonation

Thread Tools


Thorsten Schiller
Posts: n/a

I'm using impersonation in an ASPNET app, where the impersonated user is
configured in the web.config:
<identity impersonate="true" userName="userWithAppropiateRightsForTheApp"

So far, so good. It seems to work in come ways, i.e. the app can access a
network share which cannot be accessed by the ASPNET account. The ASPNET
account is still configured in the machine.config, but the account was added
to the Administrators group (to enable impersonation thru LogonUserA, see

<processModel ...userName="machine" password="AutoGenerate" .../>

But, when I call System.Diagnostics.Process.Start("LegacyApp.exe", "args"),
LegacyApp runs in the ASPNET account! This is still true if I impersonate
the user with Win32 API calls (LogonUserA, DuplicateToken, ...).

I don't understand this. What does impersonation means? Which code is
executed in the impersonated account and which not? Is there a way to spawn
a process from an ASPNET app that runs in an account that I specify?

Any help is appreciated.

Thanks, Panther.

Reply With Quote

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Impersonation code Pramod ASP .Net 1 05-12-2005 09:56 PM
Problem with impersonation and delegation Kelly D. Jones ASP .Net 1 09-12-2003 04:43 PM
Re: ASP.NET Fails after SP4 with Impersonation Hidulf ASP .Net 1 06-30-2003 05:23 PM
Re: ASP.NET Fails after SP4 with Impersonation Raymond Basque ASP .Net 3 06-29-2003 05:18 PM
RE: ASP.NET Fails after SP4 with Impersonation Bassel Tabbara [MSFT] ASP .Net 1 06-28-2003 12:01 AM