June 2026 - Koha-bugs - lists.koha-community.org

[Bug 42366] debug_mode 0 and debug_mode 1 enable debug mode
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

1 0

[Bug 37598] New: Ability to use the BCC field for sending notices to multiple addresses, rather than the To field
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37598 Bug ID: 37598 Summary: Ability to use the BCC field for sending notices to multiple addresses, rather than the To field Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Bug 12802 allows libraries to select a list of email address fields to use when sending notices to patrons. You would check all of the email addresses you want to use in a new system preference EmailFieldSelection and Koha will send the notice to all of those addresses. However, all of those addresses do go through in the To field. They are not in the BCC field. It would be good to enable the option to use the BCC field for the email addresses rather than the To field. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 38940] New: ConsiderLibraryHoursInCirculation set to "shorten the loan period and set the checkout to be due at the library’s close time" does not appear to work
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38940 Bug ID: 38940 Summary: ConsiderLibraryHoursInCirculation set to "shorten the loan period and set the checkout to be due at the library’s close time" does not appear to work Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If I have ConsiderLibraryHoursInCirculation set to "shorten the loan period and set the checkout to be due at the library’s close time" and check out an item whose loan period should be shortened to account for closing hours, the loan period isn't being shortened as expected. To replicate: -Set ConsiderLibraryHoursInCirculation to "shorten the loan period and set the checkout to be due at the library’s close time" -Set Library A's hours from any opening time (I used 8a) to 12p -Set a circ rule for all patron types/test item type for hourly loans using the number of hours that would go past your closing time (test: 3 hours) -Check out the test item type at a time when the loan period should be shortened (test: 11.30a) -Note that the loan period is not shortened (test: 2.30p) despite the closing time and system preference -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 42924] New: Restore default MaxAge for CSRF token
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42924 Bug ID: 42924 Summary: Restore default MaxAge for CSRF token Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Bug 17110 lowered the default MaxAge for the CSRF token from 1 week to 8 hours, but that has led to increased usability problems for negligible security gains. I propose to restore the default which is closer to the per-session approach for CSRF tokens which tends to be the default in many web frameworks like Django. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 42942] New: Add OpenLDAP integration so Koha can be an LDAP backend
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42942 Bug ID: 42942 Summary: Add OpenLDAP integration so Koha can be an LDAP backend Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Using OpenLDAP and slapd-perl, we should be able to make Koha be an LDAP backend. This is useful for situations where you want Koha to be the user directory (AKA source of truth). As I note on bug 25796, previously I created a Keycloak extension to use a Koha API for authenticating users (see https://gitlab.com/minusdavid/keycloak-user-storage-koha) but really... if Koha had a LDAP server available, I could've just federated Keycloak off that. Likewise other OIDC systems like Dex can federate off LDAP. Having Koha able to be an LDAP backend would make SSO integrations much simpler and more standard. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 41671] New: OAuth2 authorization code grant for REST API
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41671 Bug ID: 41671 Summary: OAuth2 authorization code grant for REST API Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com At the moment, we only allow app-to-app access via HTTP Basic Auth or OAuth2 client credentials. This gives third-party apps access to a lot of functionality and data across all users. This has data privacy/security implications. Ideally, it would be great if third-party apps could require users to integrate with Koha using an OAuth2 authorization code grant, so that the third-party app could get access tokens scoped to the individual user which authenticates against Koha (and not via the third-party app). The scopes applied to to the token could be limited and the user could give consent for those scopes. And most of all... the third-party app would only be able to use that token for that user. This limits what the third-party app can do and what it can see. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 25796] New: Allow REST API to use external OAuth2 authorization server
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25796 Bug ID: 25796 Summary: Allow REST API to use external OAuth2 authorization server Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au At the moment, Koha's REST API only validates tokens using the embedded authorization server Net::OAuth2::AuthorizationServer. It would be great if Koha were configured to use an external authorization server (like Keycloak). We could redirect the /token endpoint to Keycloak, or just require consumers to query Keycloak directly for access tokens I suppose. Then we'd set up Koha to either embed (or more sustainably fetch) Keycloak's public key in order to verify that the access token is coming from Keycloak. We'd then do further token validation (to make sure it's not expired, it's for the correct audience, etc). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 42733] New: Tools/ManageMarcImport_spec.ts is failing (again)
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42733 Bug ID: 42733 Summary: Tools/ManageMarcImport_spec.ts is failing (again) Initiative type: --- Sponsorship --- status: Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Continuous Integration Assignee: tomascohen(a)gmail.com Reporter: pedro.amorim(a)openfifth.co.uk -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 40467] New: t/00-deprecated.t no longer needed
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40467 Bug ID: 40467 Summary: t/00-deprecated.t no longer needed Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org it only tests for the presence of "switch" -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 41449] New: Reserves.t may fail when on shelf holds are restricted
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41449 Bug ID: 41449 Summary: Reserves.t may fail when on shelf holds are restricted Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org [1] Around line 1486, it is assumed that onshelfholds == 1. If you set the circ rule to If any unavailabe, the test fails. t/db_dependent/Reserves.t .. 60/71 # Failed test 'Item not available for item-level hold because no effective item type' # at t/db_dependent/Reserves.t line 1486. # Looks like you failed 1 test of 3. => Fix that assumption. Note btw that the lines following the error, onshelfholds is set to 0. [2] The test description is misleading and incorrect (copied from an earlier one, not adjusted) ok( C4::Reserves::IsAvailableForItemLevelRequest( $item, $patron ), "Item not available for item-level hold because no effective item type" ); => The item is available because '0' is defined. -- You are receiving this mail because: You are watching all bug changes.

1 18