The Google OpenID Connect specific functionality only targeted the OPAC. Probably because it’s the most common use case. (I wrote my own OpenID Connect integration for Koha about 10 years ago, and it only targeted the OPAC too.)
However, Koha has a different more generic Oauth2/OpenID Connect feature that targets both the OPAC and the staff interface. It should be usable with Google as well, if you want to target it. I think at some point the Google OpenID Connect specific code will be removed from Koha. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel <koha-devel-boun...@lists.koha-community.org> On Behalf Of long_sam.tw via Koha-devel Sent: Thursday, 18 April 2024 7:22 AM To: koha-devel <koha-devel@lists.koha-community.org> Subject: [Koha-devel] Google OpenID Connect Hi, all Google OpenID Connect is used in koha. Why does opac have this identity authentication login, but staff does not have this function? What is the main reason? With respect, long_sam
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
