https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42754 --- Comment #2 from Kyle M Hall (khall) <kyle@bywatersolutions.com> --- Created attachment 199841 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=199841&action=edit Bug 42754: Handle SC Status (99) messages without requiring a login The SIP2 spec does not require authentication for the SC Status ( 99 ) message and its ACS Status ( 98 ) response. In fact, the spec treats the 99 as the first message a self-check unit sends, with login being an optional exception "configurable on the SC". Koha's raw transport, however, requires a 93 Login before it will process anything else, and silently drops the connection on any other first message. That makes it impossible to check that the SIP2 server is alive and responding without a valid SIP login. With SIP2AllowSCStatusWithoutLogin enabled, the raw transport now answers a pre-login 99 with a 98 and keeps waiting for a login, rather than dropping the connection. send_acs_status falls back to safe defaults when there is no authenticated account yet: an anonymous ILS ( so the capability flags report N ), an empty institution id, and no patron existence check. This lets a monitoring tool confirm the SIP2 server is up without needing a SIP account. Test Plan: 1) Apply this patch 2) Run updatedatabase.pl 3) Restart all the things! 4) Without setting the new preference, connect to the SIP2 server and send an SC Status message before logging in: printf '9900302.00\r' | nc 127.0.0.1 6001 Note the connection is dropped with no response! 5) Set SIP2AllowSCStatusWithoutLogin to "Allow" 6) Restart all the things! 7) Send the same SC Status message again: printf '9900302.00\r' | nc 127.0.0.1 6001 8) Note you now get back a 98 ACS Status response without logging in! 9) Set SIP2AllowSCStatusWithoutLogin back to "Don't allow" 10) Restart all the things! 11) Send the SC Status message again, note the connection is dropped again! -- You are receiving this mail because: You are watching all bug changes.