Prosentient Systems
>
> 72/330 Wattle St
>
> Ultimo, NSW 2007
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> *From:* Michael Hafen (TECH)
> *Sent:* Saturday, 8 August 2020 2:46 AM
> *To:* David Cook
> *Cc:*
: 02 8005 0595
From: Michael Hafen (TECH)
Sent: Saturday, 8 August 2020 2:46 AM
To: David Cook
Cc: Koha Devel ; Kyle Hall
; Tomas Cohen Arazi
Subject: Re: [Koha-devel] Best practices for using Koha APIs server-side by Koha
Maybe I'm lacking in imagination, but I can only think of two cases
Maybe I'm lacking in imagination, but I can only think of two cases where a
Koha to Koha api would be useful: scheduled tasks (cron, et. all), and
command line scripts. I think in both of these cases it's feasible to
avoid auth entirely since it is basically jumping right into Koha at the
control
Hi all,
I mostly see Koha APIs being used client-side by Koha using cookie
authentication.
I know we have OAuth2 and Basic Auth that can be tied to a Koha user, and
used by a third-party system, which is great.
However, what about when we have server-side Koha components that want to
