https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42652 Bug ID: 42652 Summary: Add per-account option to allow restricted patrons to retain SIP inet access Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs@lists.koha-community.org Reporter: martin.renvoize@openfifth.co.uk QA Contact: testopia@bugs.koha-community.org This patch adds a new per-account SIP2 configuration flag, `patron_restriction_blocks_inet`, that controls whether a patron with an account restriction (debarment) also has their SIP inet profile blocked. Currently, when a patron is restricted in Koha, the SIP inet field (FID_INET_PROFILE) is set to N. This means online services that use SIP for authentication â such as PC booking systems or printing services â also deny access to the restricted patron. Libraries that want to block a patron from borrowing items but still allow them to use digital services have no way to achieve this. With this flag set to 0/false on a SIP2 account, restricted patrons will receive Y for inet access, allowing them to authenticate to online services, while checkout privileges remain blocked as normal. The default (NULL or true) preserves existing behaviour: restrictions block both checkouts and inet access. Test plan: 1. Apply all patches and run the database update. 2. Go to Administration > SIP2 accounts and edit an account. 3. Confirm the new "Restrictions block internet access" toggle is visible. 4. Create a test patron and apply an account restriction to them. 5. With the toggle unset (default), authenticate the patron via SIP and confirm the patron status response shows charge privileges denied AND inet profile N. 6. Set the toggle to false/disabled for the account and re-authenticate. 7. Confirm the patron status response still shows charge privileges denied but inet profile is now Y. 8. Confirm a non-restricted patron is unaffected. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.