OPAC: username that starts with a number is treated like a barcode

[Chris Sharp]

In Evergreen 2.3.6, when logging into the OPAC, a username that starts with a number is treated by the system like a barcode, but the user is only told that the login fails with no indication as to why. Obviously, the username regex setting can be used to prevent the creation of a username that starts with a number, but we need better error handling here. My naive suggestion would be when the system does not find the barcode, that it checks to see it's a username instead, but I'll leave implementation to others. ;-)

Evergreen 2.3.6
PostgreSQL 9.1
OpenSRF 2.1.2
Ubuntu 12.04 LTS

[Adam Bowling (abowling)]

Pushed a patch that runs this as it's designed now, but, upon authentication failure, tries a username beginning with a digit as a username, instead of a barcode.

lp1255561_username_begins_with_digit:user/abowling/lp1255561_username_begins_with_digit

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=e276c58a56d27fe114cd1351bed60235107395a0

[Terran McCanna (tmccanna)]

Related issue: the self-check interface doesn't follow the same behavior. It would be helpful if it was updated to match the current behavior as well as this proposed new behavior:

https://bugs.launchpad.net/evergreen/+bug/1528647

[Jessica Woolford (jwoolford)]

Any chance of getting a rebase on this branch? Still seems to be in issue. Tested on 3.6.5 and 3.8.0.