Author: Dave_Winchester | Posted on: 5/26/2010 9:17:44 AM | Views : 369

Hi all
I have a need to implement a custom membership provider into a new application I am writing at work. The applications separates UI, BLL and DAL and is based on a provider pattern design.
But all examples I find on the net are like the one above, where the security logic and data access are wired directly into the provider. Does anyone have some tips on if I try break this out or should just leave it alone for ease purposes ex:
public override bool ChangePasswordQuestionAndAnswer(string username, string password, string newPasswordQuestion, string newPasswordAnswer) { if (!ValidateUser(username, password)) return false; int status = SiteProvider.Security.ChangePasswordQuestionAndAnswer(username, newPasswordQuestion, EncodePassword(newPasswordAnswer)); ...

Go to the complete details ...