Re: Impersonation Issue
- From: "-Steve-" <nntp@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 16 Mar 2007 08:30:37 -0700
Basic auth just isn't sexy enough though ;-)
"Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Ouo%23MrsZHHA.4684@xxxxxxxxxxxxxxxxxxxxxxx
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: Joe Kaplan
- Re: Impersonation Issue
- References:
- Impersonation Issue
- From: -Steve-
- Re: Impersonation Issue
- From: Joe Kaplan
- Impersonation Issue
- Prev by Date: Re: Adding attributes in Active Directory
- Next by Date: Re: Impersonation Issue
- Previous by thread: Re: Impersonation Issue
- Next by thread: Re: Impersonation Issue
- Index(es):
Relevant Pages
|
|