The ActiveDirectoryMembershipProvider class inherits MemberhipProvider.
This means that you do not need to bind your application to AD as such, but to the MembershipProvider model. This model is used throughout .net and works well with built-in controls and classes.
Here is an example
//Any of these will work ActiveDirectoryMembershipProvider provider = new ActiveDirectoryMembershipProvider(); //SqlMembershipProvider provider = new SqlMembershipProvider(); //MyCustomMemebershipProvider provider = new MyCustomMemebershipProvider(); MembershipProvider membershipProvider = provider; if (membershipProvider.ValidateUser("username", "password")) { MembershipUser user = membershipProvider.GetUser("username", true); } else { //Do something }
I am not an expert in this model, but I had some experience with the MembershipProvider subclass and implementing IPrincipal, IIdentity, etc. It is truly flexible and supports a consistent architecture.
source share