Re: [Taler] auth doesn't seem to have effect

[Sebastian Javier Marchano]

Try against the /private paths like /private/instances.

$ curl -i -H "Authorization: ApiKey sandbox" https://backend.demo.taler.net/private/instances | head -n 1
HTTP/1.1 200 OK

$ curl -i -H "Authorization: piKey sandbox" https://backend.demo.taler.net/private/instances | head -n 1
HTTP/1.1 401 Unauthorized

$ curl -i -H "Authorization: ApiKey sandbox123" https://backend.demo.taler.net/private/instances | head -n 1
HTTP/1.1 200 OK

For the last one it seems that there is a bug.

--
Sebastian

On Thu, 11 Feb 2021 at 20:39, Thien-Thi Nguyen <ttn@gnuvola.org> wrote:

Please find attached a small session log:

that seems to demonstrate that the auth headers are not taken
into account at all (the result is always response 200).  That
seems to go against the documentation, which states that the
auth header must be {"Authorization": "ApiKey sandbox"} for
things to proceed normally.  What am i missing?

--
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)               ; (2021) Software Libero
   (pcase (context query)               ;       = Dissenso Etico
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502