Home/ Questions/Q 77397
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T20:49:26+00:00

I’m writing a custom MembershipProvider for a legacy database. Users are authenticated by login

  • 0

I’m writing a custom MembershipProvider for a legacy database. Users are authenticated by login and password, there is no e-mail attribute attached. What is the best way to ‘short-cycle’ the FindUsersByEmail() and GetUserNameByEmail() methods? My naive approach was to leave them unimplemented, since I assume if there is no need to restore a password, there is also no need to look up users by e-mail — does this have any side effects?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I would hazard a guess that you will be okay. A quick look at the dependcies in Reflector shows that these methods are only used by static methods of the Membership class.

    However since these are public methods other 3rd party controls / APIs may assume they are implemented. It seems this is the case with some of the SharePoint API (see the private methods in grey) SPMembershipProviderPrincipalResolver uses both of these methods.

    http://img143.imageshack.us/img143/7097/windowclipping3rn3.png

    • 0