Re: AD Login failure when using ActiveDirectoryMembershipProvider
- From: "Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 23 Feb 2007 09:34:22 -0600
I agree with Dominick. Use the app pool identity and create separate app
pools for each app if you need different credentials.
Also, in many cases you don't need to use a fixed domain account for the app
pool since the app pool runs as network service by default. Network service
IS a domain account when accessing resources on the network (the machine's
domain account), so this is often all you need.
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
--
"Craig Wagner" <MSDNNospam207@xxxxxxxxxxxxx> wrote in message
news:0EFE846A-CDC4-475A-BC84-C217B8A02DD3@xxxxxxxxxxxxxxxx
Let me correct my previous statement.
That IS how we configure machines at the client site, and have been
configuring them for over a year.
Perhaps it is not how we SHOULD be configuring them, but that's a
different
issue.
"Dominick Baier" wrote:
No - thats not how you would configure an IIS6 -
you would configure the app pool to run as a domain account and use no
impersonation.
.
- References:
- Re: AD Login failure when using ActiveDirectoryMembershipProvider
- From: Dominick Baier
- Re: AD Login failure when using ActiveDirectoryMembershipProvider
- From: Dominick Baier
- Re: AD Login failure when using ActiveDirectoryMembershipProvider
- Prev by Date: Re: Forms authentication - clean cookie when close browser
- Next by Date: Re: Basic password security question
- Previous by thread: Re: AD Login failure when using ActiveDirectoryMembershipProvider
- Next by thread: Re: AD Login failure when using ActiveDirectoryMembershipProvider
- Index(es):
Relevant Pages
|