I'd normally say that a pure in-db solution would be preferable to maintain as much separation between the business logic code and the stored passwords, but Galen's approach changes the least amount of code to get the job done, and that's more important for a quick release. Less lines of new code means fewer chances for bugs.
I'd normally say that a pure in-db solution would be preferable to maintain as much separation between the business logic code and the stored passwords, but Galen's approach changes the least amount of code to get the job done, and that's more important for a quick release. Less lines of new code means fewer chances for bugs.
Here's my pile-on sign-off:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/collab/ miker/lp1579225 _patron_ registration_ password_ mgmt_signoff2