Hi Michael,
We have encountered similar problems with Shibboleth. However, the community has helpfully written an upstream fix for preventing borrowers.updated_on being filled with 0000-00-00 when a new patron is created via LDAP or Shibboleth: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36822
So if you can upgrade from 24.05.03 to 24.05.06 (to get the 36822 fix) you might be able to stop future invalid borrowers.updated_on data being written to the Koha database.
I hope this helps!
Thanks,
Alex
Hi
In an installation of Koha 24.05.03 I am successfully authenticating against an LDAP server which is writing the data of the authenticating user into the Koha database. But as soon as I search for the added user in the staff client I get the message: "500: Internal Server Error. Month out of range." This is because table field "borrowers.updated_on" is automatically filled with the value "0000-00-00 00:00:00".
I am aware of bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31143 (We should attempt to fix/identify all cases where '0000-00-00' may still remain in the database) but of course it is not possible to manually change the value of field "borrowers.updated_on" from "0000-00-00 00:00:00" to NULL every time a user successfully logs into the OPAC.
So I tried to set the value of "borrowers.updated_on" by using lines like the following, but unfortunately they all resulted in the invalid value "0000-00-00 00:00:00".
<updated_on is="">NULL</updated_on>
<updated_on is="potato"></updated_on>
<updated_on is="">2024-11-18 00:00:00</updated_on>
How can I prevent Koha filling in this invalid value when authenticating against LDAP and instead generate a NULL value?
Best wishes: Michael