Bug 19701

Summary: Modify patron loses password in Microsoft Edge
Product: Koha Reporter: Emma Perks <emma.perks>
Component: Browser compatibilityAssignee: Owen Leonard <oleonard>
Status: CLOSED INVALID QA Contact: Testopia <testopia>
Severity: minor    
Priority: P5 - low CC: dcook, katrin.fischer, r.delahunty
Version: 16.05   
Hardware: PC   
OS: Windows   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Emma Perks 2017-11-27 16:35:55 UTC
In Microsoft Edge editing a patron record takes away the password and you have to add it back in before you can save the record.
Comment 1 Ray Delahunty 2018-10-11 11:16:40 UTC
Our experience is somewhat different. When we edit any user record rather than the passwords vanishing they change from 4 asterisks and 4 asterisks (Password and Confirm Password) to 4 asterisks and 11 asterisks. Then the password length mismatch results in a standard error that the passwords do not match and the record cannot be edited without clearing both password fields. We are not actually using passwords, relying instead on LDAP, but we were planning to have library staff add a local password to their record so when our LDAP server fails then there is a fallback password, allowing staff to log in. This change will not work properly in Edge.
Comment 2 Katrin Fischer 2019-02-10 13:35:50 UTC
(In reply to Ray Delahunty from comment #1)
> Our experience is somewhat different. When we edit any user record rather
> than the passwords vanishing they change from 4 asterisks and 4 asterisks
> (Password and Confirm Password) to 4 asterisks and 11 asterisks. Then the
> password length mismatch results in a standard error that the passwords do
> not match and the record cannot be edited without clearing both password
> fields. We are not actually using passwords, relying instead on LDAP, but we
> were planning to have library staff add a local password to their record so
> when our LDAP server fails then there is a fallback password, allowing staff
> to log in. This change will not work properly in Edge.

This usually happens when the password for Koha was saved in the browser. Removing it, can help avoid the issue on the circulation desk.

Emma, since this has been 2 years (and I can't test with Edge :( ), could you test if this is still an issue?
Comment 3 David Cook 2019-02-12 02:14:00 UTC
I've heard of related issues in Microsoft browsers but have never reproduced them. Curious to hear more...
Comment 4 Owen Leonard 2019-02-14 19:59:06 UTC
I am unable to reproduce this problem. Because this report has gone so long without an update I'm going to consider it invalid.
Comment 5 David Cook 2019-02-14 23:57:11 UTC
(In reply to Owen Leonard from comment #4)
> I am unable to reproduce this problem. Because this report has gone so long
> without an update I'm going to consider it invalid.

I feel like it's an issue with the browser as well. I'm not sure there is anything Koha could do even if we wanted to?
Comment 6 Emma Perks 2019-02-15 10:32:56 UTC
Hi all, 

Yes, this can be marked resolved, as we're not going down the Microsoft Edge route across our organisations so I've not tested this further. 

Many thanks.