Reproduce: 1. Go to OPAC 2. Login with the database user 3. Observe Internal Server Error Check your logs: Can't call method "is_debarred" on an undefined value at /home/koha/kohaclone/opac/opac-user.pl line 96.
Created attachment 63101 [details] [review] Bug 18538: OPAC databse user login internal server error Reproduce: 1. Go to OPAC 2. Login with the database user 3. Observe Internal Server Error Check your logs: Can't call method "is_debarred" on an undefined value at /home/koha/kohaclone/opac/opac-user.pl line 96. This patch fixes the mentioned crash. To test: 1. Reproduce the issue with above test plan 2. Apply this patch 3. Go to OPAC 4. Login with the database user 5. Observe successful login
Created attachment 63134 [details] [review] Bug 18538: OPAC databse user login internal server error Reproduce: 1. Go to OPAC 2. Login with the database user 3. Observe Internal Server Error Check your logs: Can't call method "is_debarred" on an undefined value at /home/koha/kohaclone/opac/opac-user.pl line 96. This patch fixes the mentioned crash. To test: 1. Reproduce the issue with above test plan 2. Apply this patch 3. Go to OPAC 4. Login with the database user 5. Observe successful login Bug reproduced, is fixed by this patch. Signed-off-by: Marc Véron <veron@veron.ch>
Why do you want to login at the OPAC with the DB user?
(In reply to Jonathan Druart from comment #3) > Why do you want to login at the OPAC with the DB user? I was wondering the same, but previously it has been possible with a warning message displayed for the user. This error was caught by one of our PageObject tests.
I'd prefer to handle the error (more or less gracefully) raising an exception from C4::Auth, rather than assuming that it's possible to login with this user.
(In reply to Jonathan Druart from comment #5) > I'd prefer to handle the error (more or less gracefully) raising an > exception from C4::Auth, rather than assuming that it's possible to login > with this user. Make me think to "Bug 18403: Add sub output_and_exit_if_error - unknown_patron & cannot_see_patron_infos"
I can't replicate the internal server error in current versions. I only get: Staff: Error: Invalid username or password OPAC: You entered an incorrect username or password. I believe this is ok then.