Session Hijack problem?

S

SCG

Hi,

I am using forms auth.

I want a support guy to be able to "impersonate" a user by logging on as
them automatically. This logon manifests itself as a 2nd browser window
launched on the support guys desktop. I want both browser windows to
"remember" who they are logged on as.

So, the support guy logs on, and I store the intenal user id as the forms
cookie (using say FormsAuthentication.SetAuthCookie(supportGuyId.ToString(),
False)).

From then on I can use the HttpContext.Current.User.Identity.Name to get the
ID of the support guy. Harrah.

So, from a grid of users I select one and launch a new window (under the
same IE process which may be the problem...) and this logs me on as the new
user....doing another
FormsAuthentication.SetAuthCookie(newUserGuyId.ToString(), False))

BUT...

then I go back to the 1st window (support guy) and navigate to another page
and magically see only the new guys stuff....

i.e. HttpContext.Current.User.Identity.Name which I use for the "key" on the
original browser window returns the ID of the user launched in the new
window!!!

My question is, "Is HttpContext.Current.User.Identity bound to the (IE6)
process only?"

If so, are there any other approaches I could use to get round this short of
having an invisible Frame on the page holding just the user index.

Ideally I' like the IE browser to launch in another process, but I believe
even if I could do that Firefox et al don't take that approach.


Thanks for any help?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,769
Messages
2,569,580
Members
45,055
Latest member
SlimSparkKetoACVReview

Latest Threads

Top