---- Reported by oftl@critfc.org 2009-05-19 15:47:15 ---- Add OpenID as a patron authentication option for OPAC. --- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:08 UTC --- This bug was previously known as _bug_ 3237 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3237 Unknown operating system Windows 2000. Setting to default OS "All". Actual time not defined. Setting to 0.0
Is adding openid authentication still sponsored and seeking a developer?
See also: http://wiki.koha-community.org/wiki/Alternative_OPAC_logins_RFC
After no answer in a long time, I'm willing to implement this, so I'll adopt it and set the status to Seeking Cosponsors. Any sponsors reading this? Please get in touch, either here, directly or http://www.software.coop/contact/
I was going to say that I'm doing work on OpenID...but I realized that I'm actually working on "OpenID Connect Core 1.0" which is a veneer over OAuth2.0 rather than being an implementation of "OpenID Authentication 2.0". I assume that you're talking about "OpenID Authentication 2.0". In any case, I think that Koha needs a better API for handling external authentication...
Is this resolved by bug 10988?
(In reply to Katrin Fischer from comment #5) > Is this resolved by bug 10988? I doubt it. OpenID Connect and OpenID are two completely separate beasts, I believe. Plus, I think bug 10988 is hard-coded just to work with Google, unfortunately. I always meant to provide a generic OpenID Connect auth plugin, but never had the time/money...
So I think that OpenID Connect represents the evolution of OpenID and that this bug could probably be closed and maybe marked as duplicate of https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21586
*** This bug has been marked as a duplicate of bug 21586 ***