https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17004
--- Comment #23 from Martin Renvoize <[email protected]> --- I was actually suggesting Koha act as an OAuth/OpenID Connect provider rather than just a consumer. There's pretty solid Mojolicious Plugin we could use that gives us a chunk of this out of the box: https://metacpan.org/pod/Mojolicious::Plugin::OAuth2::Server It's using something like this that I'm advocating ;) So, when logging in the user would get directed to a Koha login page and then redirected back to whatever SSO consumer they came from. It's clearer to the user what login they should be using and who the original party is that's storing their authentication credentials. OAuth is of course the 'Authorization' side of the story, we'd still need to work out the OpenID Connect side of the story to bring this back down to simple 'user identification'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
