https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38772
David Nind <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |Main CC| |[email protected] --- Comment #3 from David Nind <[email protected]> --- I've signed off, as it does appear to be a typo, and there is no minPasswordPreference system preference. However, this change makes no difference in actually resetting your password. Question for QA: So is this code still required/redundant/something else going on? I tested the OPAC password recovery process before and after applying the patch, and it worked as expected. I'm not a developer, so I have no idea how the underlying code works! Testing notes (KTD): 1. In the staff interface, check that the minPasswordPreference system preference DOES NOT exist. 2. In the staff interface, check that minPasswordLength system preference DOES exist (default is set to 8). 3. Set OpacResetPassword system preference to "Allow". 4. Set up KTD so that you can send emails [1]. 5. Add an email address to a patron, and change their credentials/password so that you can log in to the OPAC as that patron. 6. In the OPAC (logged out), select the "Forgot your password?" link, enter card number/user name, or email address. 7. Use the link in the email to reset the password. 8. Note that if the password length is less than the minimum length (before and after the patch), you can't reset your password unless it meets the minimum length. [1]. To test sending emails using a Google account: 1. Set up an App password for your Google Account. 2. Configure a new 'SMTP Server' under 'Administration > SMTP servers' using the following settings, where `User name` = your Google email address and `Password` = your APP password, not your Google account password): Host: smtp.gmail.com Port: 587 Timeout: 5 SSL: STARTTLS User name: GOOGLEACCOUNTUSER Password: GOOGLEAPPPASSWORD Debug mode: Enabled Default server: selected -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
