Local debugging as different user

[ThatRickGuy]

I have an intranet web site that uses integrated windows security. Part of the site opperates differently depending on who is logged in. What I would love to do is launch the page in debug mode, then supply the credentials of the account that is having problems. But the troubled account doesn't have developer/debugger rights. Is there some easy way to do this?

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[ca8msm]

How about using impersonation?


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[BoulderBum]

Can you log into your machine as the troubled user (after temorarily granting said user the appropriate rights to your machine), then run the Visual Studio debugger?

Alternately, you could have them log into a test server then attach to that server's ASP.NET process. Note that you really don't want to do this on a production server because 1) it would require enabling remote debugging on the server which is a security risk and 2) it would stop the process for every user trying to access the site.

Also, you can, as Ca8msm suggested, add code to your application (perhaps in Global.asax on AuthenticateRequest or something) where it switches your IPrincipal to impersonate that of the user in question.