Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Extending AspNetMembershipProvider to facilitate external authenticationExtending AspNetMembershipProvider to facilitate external authentication
Previous
 
Next
New Post
12/30/2007 9:40 AM
 

I am working on integrating DNN4.7 with LDAP for the intranet in the company I work for.  After following a few threads and looking into the code  I end up  on the AspNetMembershipProvider class.  For my purpose all I need to do is replace the functionality of ValidateUser( )  and ChangePassword( ).  ChangePassword( ) is overridable but ValidateUser() is not.  I addressed my problem by modifying the source code for AspNetMerbershipProvider and making ValidateUser protected and overridable.

Since AspNetMemrbershipProvider can serve as the base class for most efforts requiring external authentication, would it be possible in future versions of DNN to make private methods protected and overridables?

The articles I found on this subject promote clipboard inheritance of AspNetMembershipProvider (copy and paste for the object oriented challenged) as opposed to true inheritance.  A great deal of functionality is packed in this class that I do not want to replicate to be able to authenticate users externally.  Also there is the issue of keeping up with updates.  My approach will required modifications to the 4.8 source code when I am ready to upgrade, but that would not be necessary if the ASPNetMembershipProvider class was refactored to allow  selective modification.

 

 
New Post
1/2/2008 10:10 AM
 

Personally, Depending on your implementation you might be able to get by using an AuthenticationProvider which is supported in DNN 4.6 and later.

Otherwise you are right that the only current method is to copy/paste to create your own provider, or rewriting the provider...


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Extending AspNetMembershipProvider to facilitate external authenticationExtending AspNetMembershipProvider to facilitate external authentication


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out