Looks like I had cgid_module and suexec_module on 20.05 enabled in
addition to what you have, but disabling them did not help.
--Ere
Tomas Cohen Arazi kirjoitti 26.5.2021 klo 15.20:
So maybe it is a side effect of using some authentication module in Apache?
This is from a 20.05 setup, that I
So maybe it is a side effect of using some authentication module in Apache?
This is from a 20.05 setup, that I know OAuth2 is being used by a vendor:
$ sudo apache2ctl -D DUMP_MODULES
Loaded Modules:
core_module (static)
so_module (static)
watchdog_module (static)
http_module (static)
log_co
Aswin,
Yes, I got that. Sorry, I meant to address my question to Tomas.
Best,
Ere
Aswin Unnikrishnan kirjoitti 26.5.2021 klo 10.11:
No, I mean it was *not* working with default configurations. I kept
getting a 401 error.
I had to add an extra line to the apache config file like mentioned in
No, I mean it was *not* working with default configurations. I kept
getting a 401 error.
I had to add an extra line to the apache config file like mentioned in the
documentation you provided earlier, to make apache pass the Authorization
headers.
On Wed, May 26, 2021, 11:58 AM Ere Maijala wro
Do you mean OAuth2 is working for you without anything special in Apache
config? I've not been that fortunate yet, though it might depend on
whether authentication plugins are enabled in Apache.
--Ere
Tomas Cohen Arazi kirjoitti 22.5.2021 klo 18.15:
I wonder why it is working out of the box, a
Debian Linux 9 and koha 19.11
On Sun, May 23, 2021, 6:02 PM Tomas Cohen Arazi
wrote:
> OS anda Koha version?
>
> El dom., 23 may. 2021 1:06 a. m., Aswin Unnikrishnan <
> aswinunn...@gmail.com> escribió:
>
>> Nope, were using the default apache configurations. Nothing special
>>
>> On Sat, 22 May
OS anda Koha version?
El dom., 23 may. 2021 1:06 a. m., Aswin Unnikrishnan
escribió:
> Nope, were using the default apache configurations. Nothing special
>
> On Sat, 22 May 2021 at 20:46, Tomas Cohen Arazi
> wrote:
>
>> I wonder why it is working out of the box, and not for you. Is there any
>
Nope, were using the default apache configurations. Nothing special
On Sat, 22 May 2021 at 20:46, Tomas Cohen Arazi
wrote:
> I wonder why it is working out of the box, and not for you. Is there any
> special apache config you're using?
>
> If not, then this is something we should patch in the Ko
I wonder why it is working out of the box, and not for you. Is there any
special apache config you're using?
If not, then this is something we should patch in the Koha packages for
everyone.
Kind regards
El sáb., 22 may. 2021 12:12, Aswin Unnikrishnan
escribió:
> Thank you so much guys,
>
> Wa
Thank you so much guys,
Was a bit busy the past couple of days and could'nt work on it. But I
followed the documentation mentioned by Ere and it worked!
SetEnvIf Authorization .+ HTTP_AUTHORIZATION=$0
If anyone else faces this issue, you should add this command under
Tag .
Thanks,
Aswin
On
ftware Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
-Original Message-
Date: Wed, 19 May 2021 11:49:48 +0300
From: Ere Maijala
To: koha@lists.katipo.co.nz
Subject: Re: [Koha] Koha API - Authentication Fai
My documented steps to make sure OAuth2 is working are here:
https://github.com/vufind-org/vufind/blob/dev/config/vufind/KohaRest.ini#L20
This may be useful for you. I suppose it would make sense to document
this properly in Koha wiki as well, I just haven't had time...
Best,
Ere
Aswin Unnik
Check the plack*.log files in the logs
El lun., 17 may. 2021 14:53, Aswin Unnikrishnan
escribió:
> Thanks for pointing that out Stephen, I will have to look into that, it
> might be the issue here.
>
> Tomas, I am not exactly sure if we have plack running or not. Plack seems
> to be enabled, bu
Thanks for pointing that out Stephen, I will have to look into that, it
might be the issue here.
Tomas, I am not exactly sure if we have plack running or not. Plack seems
to be enabled, but plack logs are all empty. the logs are all at
intranet-error.log and opac-error.log
I will try out the apa
Are you running Plack?
El lun, 17 may 2021 a las 11:53, Aswin Unnikrishnan ()
escribió:
> Thanks Stephen, Tomas for the quick response.
>
> Aswin - are you using the correct URL to call your custom endpoint. It
>> should be under the contrib namespace e.g.
>>
>
> The app i am making is not part o
Arazi ; Stephen Graham
Cc: Discussion Group Koha
Subject: Re: [Koha] Koha API - Authentication Failure
Thanks Stephen, Tomas for the quick response.
Aswin - are you using the correct URL to call your custom endpoint. It should
be under the contrib namespace e.g.
The app i am making is not part of
Thanks Stephen, Tomas for the quick response.
Aswin - are you using the correct URL to call your custom endpoint. It
> should be under the contrib namespace e.g.
>
The app i am making is not part of koha, its a seperate web app which makes
calls to /api/v1/ end points of the koha server.
Does th
Does the user (owner of the id/secret pair) have privileged access to Koha?
Remember it needs to have permissions to enter the staff interface (the
'catalogue' permission) in order to access routes (other than those in the
/api/v1/public namespace).
BTW: All routes also have some required permissi
Aswin - are you using the correct URL to call your custom endpoint. It should
be under the contrib namespace e.g.
https:///api/v1/contrib/
Stephen
-Original Message-
From: Koha On Behalf Of Aswin Unnikrishnan
Sent: 17 May 2021 13:40
To: Discussion Group Koha
Subject: [Koha] Koha API
19 matches
Mail list logo
