https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30962
--- Comment #13 from David Cook <[email protected]> --- While I originally created this to support a Keycloak User Storage SPI extension, I've had libraries interested in it as an alternative to the ILS-DI API "AuthenticatePatron" verb. It's essentially the 1 thing that the ILS-DI API can do that the REST API can't do, which means that libraries use the ILS-DI API (or SIP2) to authenticate patrons against the Koha database for third-parties software. So it would be great to get this into Koha core, so that we can continue to move away from the ILS-DI API. -- We've actually had more and more libraries using Keycloak with the Koha user storage extension, because it means they get to-purpose software for SSO, while still getting to manage all their patrons in Koha. It's super useful. (I also have a goal of Koha using Keycloak Oauth2 access tokens to bring SSO to Koha's REST API, so that third-parties could call public API endpoints on behalf of Koha users without third-parties needing dedicated API users with staff-level permissions, which would be a massive improvement on security/trust relationships, but one step at a time...) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
