Impersonation Issue

From: "-Steve-" <nntp@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 14 Mar 2007 13:52:24 -0700

I'm using asp.net 2.0 login control to authenticate my users against AD.
I'm storing their encrypted password in session state, which I then pass to
the LogonUser method and succesfully impersonate their account.

The problem I'm having is that I have to continually re-impersonate the user
on every postback. Is there a better solution?

Steve

.

Follow-Ups:
- Re: Impersonation Issue
  - From: Joe Kaplan

Prev by Date: Using Protocol Transition and Constrained Delegation to access a domain controler via LDAP
Next by Date: Re: Active Directory Membership Provider Change Password
Previous by thread: Using Protocol Transition and Constrained Delegation to access a domain controler via LDAP
Next by thread: Re: Impersonation Issue
Index(es):
- Date
- Thread

Relevant Pages

Impersonation Issue
... I'm storing their encrypted password in session state, ... the LogonUser method and succesfully impersonate their account. ...
(microsoft.public.dotnet.framework.aspnet)
Re: DataSet across more than 1 page
... > object data without using hardware. ... Ryu might want to try just storing the tables that are ... ASP.NET stores session state in the same process, ... the most serious issue with ASP session state is not present ...
(microsoft.public.dotnet.framework.aspnet)
Session VS. ViewState For Small Value
... storing a small value in the ViewState vs. Session state. ... the 3rd obvious option - cookies. ...
(microsoft.public.dotnet.framework.aspnet)