[Bug 12267] New: Allow password option in Patron Attribute non functional
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12267 Bug ID: 12267 Summary: Allow password option in Patron Attribute non functional Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs@lists.koha-community.org Reporter: joy@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com When adding (or editing) a Patron Attribute, the option to "Allow password" can be selected. The purpose here is to allow this attribute/password to be a secondary login for the patron account. [ Allow password: Check to make it possible to associate a password with this attribute ] However, checking the box and then adding a patron with an attribute/password combination does not allow the patron to log on using that attribute password combination. 1. Set up New Patron Attribute, clicking Allow password option. 2. Create a new patron. Enter patron data including the attribute and password value 3. Save patron 4. Using that attribute/password values, attempt to log on to the OPAC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12267 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hi Joy, I am not sure if that was the purpose of the field. The way someone explained it to me in the past was, that it allows you to store a password for another application. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12267 --- Comment #2 from Galen Charlton <gmcharlt@gmail.com> --- (In reply to Katrin Fischer from comment #1)
Hi Joy, I am not sure if that was the purpose of the field. The way someone explained it to me in the past was, that it allows you to store a password for another application.
Actually, Joy's right - the original intent was to support secondary logins. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12267 Jonathan Druart <jonathan.druart@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@biblibre.co | |m --- Comment #3 from Jonathan Druart <jonathan.druart@biblibre.com> --- (In reply to Galen Charlton from comment #2)
(In reply to Katrin Fischer from comment #1)
Hi Joy, I am not sure if that was the purpose of the field. The way someone explained it to me in the past was, that it allows you to store a password for another application.
Actually, Joy's right - the original intent was to support secondary logins.
http://lists.koha-community.org/pipermail/koha-patches/2008-May/000988.html - password_allowed (if set, staff patron editor will allow a password to be associated with a value; this is mostly a hook for functionality to be implemented in the future. Does it mean we should keep it or the feature won't never be implemented and we can remove the 2 columns in DB? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12267 Jonathan Druart <jonathan.druart@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|3.14 |master -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org