[Koha] Failing authentication via CAS after update to Koha 21.11.09

[Michael Kuhn]

Hi

We're quite desperate since using CAS all our users can no more log into 
their Koha accounts. Is there really no way how to debug problems with 
the authentication via CAS?

We would be very happy if there is a way how to find out what Perl 
scripts "opac-user.pl" or "Auth_with_cas.pm" are really doing. 
Unfortunately they are not verbose at all and don't write anything into 
the log files. Is it possible to force these scripts to output what they 
are actually doing?

For example I tried the following in "Auth_with_cas.pm", but file 
"/tmp/perloutput.txt" stayed empty.

open STDERR, ">", "/tmp/perloutput.txt" or die "$0: dup: $!";

print STDERR "defaultcasserver: $defaultcasserver\n";
print STDERR "casservers: $casservers\n";
close (STDERR);

Best wishes: Michael
-- 
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E mik at adminkuhn.ch · W www.adminkuhn.ch



-------- Weitergeleitete Nachricht --------
Betreff: [Koha] Failing authentication via CAS after update to Koha 21.11.09
Datum: Mon, 11 Jul 2022 13:41:03 +0200
Von: Michael Kuhn <mik at adminkuhn.ch>
Antwort an: Michael Kuhn <mik at adminkuhn.ch>
Organisation: Admin Kuhn GmbH
An: Koha <koha at lists.katipo.co.nz>

Hi

We are using Debian GNU/Linux 10 with Koha 21.11.09 (after an update 
from Debian 9 and Koha 19.05.02).

Since the update the CAS authentication via Koha OPAC is no more 
working. The content of system preferences "OPACBaseURL", 
"casAuthentication", "casLogout" and "casServerUrl" has not changed; the 
new preference "casServerVersion" ist correctly set to "CAS 2 or earlier".

It is possible to successfully log into the CAS server but when trying 
to access the Koha OPAC via CAS ("Log in using a CAS account") the 
response is always "Sorry, the CAS login failed." and the user is not 
logged into his Koha account. The logs don't show no error.

I was checking all changes made in bugs 21973 22585 23771 20854 and 
28417 but to no avail.

Does anyone have an idea how to debug this problem?

Best wishes: Michael