Re: Impersonation Issue
- From: "Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 14 Mar 2007 23:26:01 -0700
That's the way it works. The way you are supposed to do this is to use
Windows authentication in the first place and let it do this for you. Basic
auth with SSL is much more simple.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"-Steve-" <nntp@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eHoAsqnZHHA.2320@xxxxxxxxxxxxxxxxxxxxxxx
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: -Steve-
- Re: Impersonation Issue
- References:
- Impersonation Issue
- From: -Steve-
- Impersonation Issue
- Prev by Date: Re: Active Directory Membership Provider Change Password
- Next by Date: Re: Active Directory Membership Provider Change Password
- Previous by thread: Impersonation Issue
- Next by thread: Re: Impersonation Issue
- Index(es):
Relevant Pages
|