[Koha] Patron Authentication - 16.05.13

[Joy Nelson]

With the move towards OO programming, I am seeing more errors result from
'bad data' in patron and item records.  I would run a check on the patrons
to be sure that they all have valid categorycodes and branchcodes.  Also,
doublecheck the date fields (dateenrolled,dateexpiry) as well to see if
anything seems amiss for that branch's patrons.

joy


On Sun, Jun 11, 2017 at 11:48 AM, Katrin <katrin.fischer.83 at web.de> wrote:

> Hi Gary,
>
> to my knowledge there is no limitation in the characters you can use for
> the password. I am trying to think of things that could affect passwords in
> the db.
>
> Did they do a patron import maybe accidentally overwriting the password?
> How to the passwords look in the db when you check with SQL? They are
> encrypted of course, but do they look 'right' or is the field empty?
>
> Sorry, don't really have an answer to the problem, hope this is helpful
> anyway,
>
> Katrin
>
>
> On 09.06.2017 18:00, Bortel, Gary wrote:
>
>> I made a point of stopping by that location with my laptop...wanting to
>> make sure there was nothing caught in a browser cache that might be the
>> problem. I could log on through the OPAC, the librarian couldn't using her
>> patron account. Back in the office this morning, I see nothing in the logs
>> that would point to an error. So, I created a new patron user. (I've been
>> avoiding playing with their instance of Koha in any way.) Hey, presto! I
>> was able to log on through the OPAC with the new credentials.
>>
>> I have no reason to believe either she or her patrons are unable to enter
>> their credentials correctly, but I've asked her to reset her password and
>> try again. Are there any special characters that do not play nicely in a
>> Koha user password?
>>
>>
>> gcb
>>
>> -----Original Message-----
>>
>> On 6/06/17 03:56, Bortel, Gary wrote:
>>
>>> Debian package on Ubuntu 16.04 with MySql 5.7.18, multi-tennant
>>> installation. Recently upgraded from 16.05.12 to 16.05.13-2
>>>
>>> Since the upgrade to 16.05.13-2, one library reports that patrons are no
>>> longer able to log on to their accounts through the opac. The error
>>> returned is "You entered an incorrect username or password. Please try
>>> again! And remember, passwords are case sensitive." The server hosting Koha
>>> has been restarted since the upgrade. I am able to log into their instance
>>> of Koha through the browser at my location using my "super user" account.
>>> The library was asked to clear the browser cache on the affected machine.
>>> Their patrons are still receiving the error message. However, I see no
>>> entries in the opac-error.log that might be related to this.
>>>
>>> Thoughts?
>>>
>>> gcb
>>>
>> hi Gary
>> i can't reproduce your bug on a 16.05.13 Koha
>>
>> have you tried creating a basic user, and attempting to login with that?
>>
>> cheers, Mason
>> _______________________________________________
>> Koha mailing listhttp://koha-community.org
>> Koha at lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>



-- 
Joy Nelson
Director of Migrations

ByWater Solutions <http://bywatersolutions.com>
Support and Consulting for Open Source Software
Office: Fort Worth, TX
Phone/Fax (888)900-8944
What is Koha? <http://bywatersolutions.com/what-is-koha/>