May 2023 - Koha-devel - lists.koha-community.org

Azure configuration for OAuth authentication with Koha
by Alex Buckley 24 May '23

24 May '23

Hi Koha community, If you have configured Koha OAuth authentication with Azure could you please let me know what did you configure as the Redirect and Reply URIs in Azure? Context: We have a library (running Koha 22.11) that is trying to setup OAuth authentication with Azure. They have configured the Koha end using the new Koha 'Administration' > 'Identity provider' pages. When this library attempt a SSO login they get a 'AADSTS00113: No reply address is registered for the application' Azure error - see attached. Should the Redirect and Reply URIs in Azure just be the Koha OpacBaseURL (with https), or something else? Thanks so much, Alex

2 4

Placing multiple record-level holds on a record
by David Cook 24 May '23

24 May '23

Hi all, I'm noticing in 22.11 that it's possible to place multiple record-level holds on a record. Do you think that's intentional? While I can understand having multiple item-level holds, having multiple record-level holds seems like a way to game the system. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

3 4

TLS connections
by Jacob Jett 23 May '23

23 May '23

Hi gang, It looks like AWS is upgrading their TLS connections from 1.0/1.1 to 1.2. Does anyone know if this will impact Koha records that point at AWS objects? Unrelated ISBD punctuation question. I've had some complaints from my staff about displaying ISBD punctuation. We use it in MARC to make sure that the metadata records are portable across multiple languages. However, I can sympathize that it doesn't look very clean in the display. Is there a Koha widget that either, let's us suppress displaying the ISBD punctuation or implements it at metadata record export time? Regards, Jacob *Jacob Jett* | Research Librarian | ASFPM 8301 Excelsior Dr. | Madison, WI 53717 tel: 608-828-3000 | desk: 608-828-6342 | floods.org <http://www.floods.org/> | *Email Jacob <jacob(a)floods.org>*

2 2

Spanish language not displaying on the staff or opac interface
by Zuniga, Victor 18 May '23

18 May '23

Hello, I am hoping someone can help me troubleshoot this issue. I first submitted the issue via Bugzilla. Katrin Fischer suggested I reached out to the listserv. You can look at the details already gathered on this issue here: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32677 I currently running on the latest version (Koha 22.11.05). Thanks, Victor Victor Zuniga | System Administrator [cid:image001.jpg@01D98974.DF97F5F0] Office | 970-221-6716 Cell | 614-596-3013 Webster House Administrative Center 301 E. Olive St., Fort Collins, CO 80524

1 0

koha-howto embedded into koha-testing-docker!
by Jonathan Druart 16 May '23

16 May '23

Hello, An info that you should spread to your Koha friends: koha-howto has been embedded into koha-testing-docker. Which means that it is available at http://localhost:8081/cgi-bin/koha/how-to.pl when your Koha container is started. Koha-howto [1] is a friendly tool for newcomers, it asks them some questions about our development process, points them to the useful resources (wiki, bugzilla, etc.), and even guides them through the Koha development process (write a patch, run the QA script, attach a patch to bugzilla, sign it off, etc.) In my opinion this is a very useful resource for new recruits or anybody who would like to have a try at writing their own patches! Please give it a shot and report any problems or suggest enhancements! Cheers, Jonathan [1] https://gitlab.com/koha-community/koha-howto/

1 0

Call for news - Newsletter May 2023
by Koha Newsletter 13 May '23

13 May '23

Hi I'm collecting news for the May 2023 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

Re: [Koha-devel] Issues sending a JSON request body in a GET request to REST API
by David Cook 12 May '23

12 May '23

In the short term, it appears I've forgotten about the "q" parameter. It takes an unencoded argument, so that's getting me where I need to go. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: David Cook <dcook(a)prosentient.com.au> Sent: Friday, 12 May 2023 4:47 PM To: 'Koha Devel' <koha-devel(a)lists.koha-community.org> Subject: Issues sending a JSON request body in a GET request to REST API Hi all, With the Koha REST API, there's "Advanced Matching" which uses a JSON body in a GET request: curl -u koha:koha --request GET 'http://127.0.0.1:8081/api/v1/patrons/' --header "Content-Type: application/json" --data-raw '{ "-or": [ { "surname": { "-like": "Acev%" } }, { "firstname": { "-like": "Hen%" } } ] }' https://wiki.koha-community.org/wiki/Koha_REST_API_Users_Guide#Advanced_Matc hing While this technically works, we really shouldn't be sending a JSON request body in a GET request. I'm working on a third-party system, and it's actually preventing me from sending GET requests with request bodies (since GET requests aren't supposed to have request bodies), so I can't actually use the API using that system's built-ins. I'll have to code a workaround. At some point, we should replace these GET requests with POSTed search queries I think. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 1

Issues sending a JSON request body in a GET request to REST API
by David Cook 12 May '23

12 May '23

Hi all, With the Koha REST API, there's "Advanced Matching" which uses a JSON body in a GET request: curl -u koha:koha --request GET 'http://127.0.0.1:8081/api/v1/patrons/' --header "Content-Type: application/json" --data-raw '{ "-or": [ { "surname": { "-like": "Acev%" } }, { "firstname": { "-like": "Hen%" } } ] }' https://wiki.koha-community.org/wiki/Koha_REST_API_Users_Guide#Advanced_Matc hing While this technically works, we really shouldn't be sending a JSON request body in a GET request. I'm working on a third-party system, and it's actually preventing me from sending GET requests with request bodies (since GET requests aren't supposed to have request bodies), so I can't actually use the API using that system's built-ins. I'll have to code a workaround. At some point, we should replace these GET requests with POSTed search queries I think. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Starting rabbitmq-server fails with Koha 22.11.05-2
by Michael Kuhn 12 May '23

12 May '23

Hi When trying to install Koha 22.11.05-2 via package installation on a completely new machine with 4 virtual CPUs, 4 GB RAM and Debian GNU/Linux 11 the following error appears: rabbitmq-server (3.8.9-3) wird eingerichtet ... Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details. invoke-rc.d: initscript rabbitmq-server, action "start" failed. ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-05-11 15:14:44 CEST; 4ms ago Process: 38141 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 38141 (code=exited, status=1/FAILURE) CPU: 1.071s Mai 11 15:14:44 koha systemd[1]: Failed to start RabbitMQ Messaging Server. Mai 11 15:14:44 koha systemd[1]: rabbitmq-server.service: Consumed 1.071s CPU time. Can someone please tell me how to solve this problem? You can see the output of "systemctl status rabbitmq-server.service" resp. "journalctl -xe" just below. 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(a)adminkuhn.ch · W www.adminkuhn.ch koha@koha:~$ sudo systemctl status rabbitmq-server.service ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-05-11 15:19:57 CEST; 3s ago Process: 41298 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 41298 (code=exited, status=1/FAILURE) CPU: 1.066s koha@koha:~$ sudo journalctl -xe ░░ An ExecStart= process belonging to unit rabbitmq-server.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit rabbitmq-server.service has entered the 'failed' state with result 'exit-code'. Mai 11 15:20:47 koha systemd[1]: Failed to start RabbitMQ Messaging Server. ░░ Subject: A start job for unit rabbitmq-server.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit rabbitmq-server.service has finished with a failure. ░░ ░░ The job identifier is 3262 and the job result is failed. Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Consumed 1.127s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit rabbitmq-server.service completed and consumed the indicated resources. Mai 11 15:20:48 koha sudo[41974]: koha : TTY=pts/0 ; PWD=/home/koha ; USER=root ; COMMAND=/usr/bin/journalctl -xe Mai 11 15:20:48 koha sudo[41974]: pam_unix(sudo:session): session opened for user root(uid=0) by koha(uid=1000)

2 2

Wiki - SPAM accounts and pages need deleting
by David Nind 11 May '23

11 May '23

Could someone who has the right permissions for the Wiki look at deleting the users who have created several pages on 4 May 2023, and delete the pages they have created? I'm also not sure what is happing with user registration - very few are coming through for accounts to be confirmed, but the recent changes page includes many accounts being created without the confirmation step. David Nind | david(a)davidnind.com m. +64 21 0537 847

3 4