Bug 20612: Make OAuth2 use patron's client_id/secret pairs
authorTomas Cohen Arazi <tomascohen@theke.io>
Wed, 18 Apr 2018 16:34:18 +0000 (13:34 -0300)
committerJonathan Druart <jonathan.druart@bugs.koha-community.org>
Wed, 9 May 2018 15:56:01 +0000 (12:56 -0300)
commit5bf71bb837239ca9e3fdf4703074caf5eff7ec52
tree74dcd277cc4ecb641d0446236fff0e2c5082627c
parent8eb9239a340e662c42f8686a4d29154cc54ec5e4
Bug 20612: Make OAuth2 use patron's client_id/secret pairs

This patch wires the OAuth related code so it leverages on the new
Koha::ApiKey(s) classes and tools introduced by bug 20568 instead of the
hardcoded entries in koha-conf.xml originally proposed by bug 20402.

To test revisit the test plan for bug 20402, and verify that it works.
But create API key pairs instead of writing them down in koha-conf.xml.
Also:
- Run:
  $ prove t/db_dependent/api/v1/oauth.t
=> SUCCESS: Tests pass!
- Sign off :-D

Sponsored-by: ByWater Solutions
Signed-off-by: Julian Maurice <julian.maurice@biblibre.com>
Signed-off-by: Benjamin Rokseth <benjamin.rokseth@deichman.no>
Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
Koha/OAuth.pm
Koha/REST/V1/Auth.pm