Currently Koha allows a user to sign in with either their cardnumber or userid Confusion can arise when a user has a username that is another users cardnumber, and vice versa We should check uniqueness across both of these fields.
We have a lot of patrons whose userid and cardnumber are the same, so I'd want to preserve that. But it does make sense to prevent a userid/cardnumber that belongs to the cardnumber/userid of another borrower...
Can you remind me the good reason behind the 2 login fields? :) If you want to use cardnumber to login why not set userid=cardnumber and always use userid as login?
(In reply to Nick Clemens from comment #0) > Currently Koha allows a user to sign in with either their cardnumber or > userid > > Confusion can arise when a user has a username that is another users > cardnumber, and vice versa > > We should check uniqueness across both of these fields. We had definitely problems with that in the past and had solved it. Could this be a regression? For our libraries Joubu's solution would not work. We have all different cases: * Libraries where the self check reads the chip number that is long, complicated and unknown to the user. They user the userid for logging into the OPAC. * Libraries that don't use the userid at all, but only use the cardnumber Koha has always supported both - I think there is no step back from that. But uniqueness must be enforced.
(In reply to Jonathan Druart from comment #2) > Can you remind me the good reason behind the 2 login fields? :) > > If you want to use cardnumber to login why not set userid=cardnumber and > always use userid as login? Like Katrin was saying, I think the cardnumber is more for machines, and userid is more for humans. At my local public library, they used to only have cardnumber for logging in, but then they created "alias" which is similar to userid I think. When I log in to my account, I use that human-friendly alias/userid, but I validate myself on the self-checkout using my card. (As I say that, I realize that the Koha self-checkout could have an option to show both cardnumber and userid logins... as you might've forgotten your card but might have your userid/password...)
(In reply to Jonathan Druart from comment #2) > Can you remind me the good reason behind the 2 login fields? :) > > If you want to use cardnumber to login why not set userid=cardnumber and > always use userid as login? The idea is that you can get your card lost or stolen, and you ask for a new one. The number in it should be different to avoid impersonation or to identify the card is no longer valid, etc.