I am working on implementing a custom membership provider that works against
an existing schema in my database and have a few thoughts/question.
The login control will automatically call the ValidateUser method of the
membership provider, so no matter how I implement the provider the only thing
the login control cares about the bool value returned by this method.
What I am confused about is there could be numerous reasons why a login attempt
failed; user is locked out, too many tries in a period of time, etc.
There is no way that I see to convey that to the control so it could display
the proper message. Other properties of the membership provider such as
PasswordStrengthRegularExpression have absolutely no effect on the login
control as well (out of the box), I would have hoped that it would
automatically somehow translate into regular expression validators, but that
doesn't seem to be the case. So it seems that I need to initialize the
login control properties with these settings out of the provider configuration
if I want them to take on the control itself.
If the only thing that the Login control does out of the box (without
manually handling events and doing the initialization as described above) is
call the ValidateUser method on the membership provider, I see no way to convey
back to the Login control why the validation
View Complete Post