It is better to use the ActiveDirectoryMembershipProvider in .NET 2.0. It
does exactly this.
If you must write it yourself, I encourage you to avoid
ADSI/System.DirectoryServices for this application. It scales very poorly
under load and may cause your app to completely fail when deployed if there
will be a significant number of users.
Our book discusses LDAP-based authentication in general in ch 12 and shows
some alternatives to using ADSI. You could take our samples and wire that
up into standard ASP.NET forms authentication to implement the rest of the
functionality (which is what you want), if you cannot use .NET 2.0 with the
membership features.
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 --
[quoted text, click to view] "satyendra" <satyendrab@gmail.com> wrote in message
news:1154612556.000551.98890@s13g2000cwa.googlegroups.com...
> Hi,
> I need to do the following.
> 1. I have an .aspx on an IIS Server that is not in the domain.It
> performs queries against the domain controller.
> 2. User enters his login and password and clicks submit
> 3. I need to authenticate him for his login, password and then redirect
> to a different url
>
> can somebody tell me how to do this in asp or aspx
> Thanks.
>