[Koha-bugs] [Bug 25965] Create SIP2 client daemon with HTTPS API endpoint

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25965

--- Comment #41 from David Cook <dcook at prosentient.com.au> ---
(In reply to Lari Strand from comment #40)
> We have also been thinking of another enhancemet for SIPoHTTP. Getting rid
> of the need to configure the SIP server configs for new/changed device
> accounts and instead using koha objects + some extra code for the SIPoHTTP
> endpoint for authenticating the accounts and thus getting rid of the extra
> work us developers have to do, managing them server side in SIPconfigs. That
> way the work of managing the device accounts would be left to just the
> librarians to do in Koha.

That does sound like a useful enhancement. 

(In reply to Lari Strand from comment #38)
> Oh ok thanks for the explanation.
> 
> These three major device manufactureres Mikroväylä, Lyngsoe systems and
> Bibliotheca all support SIPoHTTP and it has almost become a standard in that
> sense at least here. A parallel implementation that aims to do the same
> thing would be a bit overkill. If we ever intergated some of this stuff in
> Koha (not as a plugin but native support), we should pick one or the other?
> Or just leave both SIP over TLS (if doable) and SIPoHTTP implementations as
> plugins to cover local needs?

In theory, there would be model code that handles all the core SIP logic, and
the SIP server and SIPoHTTP endpoint would just be different controllers.
Easier said than done though of course.

That's cool about it becoming a standard over there. I don't think the rest of
the world is ready for SIPoHTTP, but maybe they will be one day.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.