Re: login control blues
- From: "Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 26 Sep 2007 19:09:53 -0500
If you are using the .NET 2.0 and absolutely must to do forms auth with AD,
you should use the ActiveDirectoryMembershipProvider. It does the right
stuff and eliminates most of the questions.
Whatever you do, you really don't want to use S.DS for authentication. It
scales very poorly in this scenario. The AD membership provider uses
S.DS.Protocols to work around the limitations in the underlying ADSI model
for bind authentication.
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
--
<ChandrikaHarathi@xxxxxxxxx> wrote in message
news:1190829674.047811.206100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am cross posting from another group hoping to get a feed back:
I need to build a simple web apps with login control authenticating
with AD. Looking from security point:
1. web.config : connection strings etc.
OR
2. build my own onAuthenticate method calling ... a pre-compiled dll.
The dll will be a class file that uses directoryservices to validate
user.
This is asp.net 2.0 on win2k+3
.
- Follow-Ups:
- Re: login control blues
- From: ChandrikaHarathi@xxxxxxxxx
- Re: login control blues
- References:
- login control blues
- From: ChandrikaHarathi@xxxxxxxxx
- login control blues
- Prev by Date: XPath Filter 2.0 Support? (XML Digital Signatures)
- Next by Date: feedback please on asp.net app security scenario
- Previous by thread: login control blues
- Next by thread: Re: login control blues
- Index(es):
Relevant Pages
|