https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38338
--- Comment #12 from Michał <[email protected]> --- (In reply to David Cook from comment #6) > But first we have to see if the SASL plugin works as expected hehe. True true > At the moment, for OAuth2, Koha uses Mojolicious::Plugin::OAuth2 which > requires a sysadmin to restart Koha for it to take effect. > > But I like the idea of there being a OAuth2 client in Koha so that people > could get that initial OAuth2 token response, which can then be stored and > passed to the library. Hmm, I don't think a dedicated OAuth2 library should be needed for this at all. I think that for most popular providers out there at least, one should get away with a purely JavaScript solution that'd fill up the field in the UI, that might be the cleanest and most lightweight solution. But if it's impossible, then I think it could be possible to just construct some special redirect URL that'd update the auth data for given SMTP server (or add new one depending on what user does) with the data it gets in response, and just redirect to server list. There should be no need for any kind of OAuth support library there whatsoever I imagine, just copy over the fields, which should just be standard access_token, refresh_token, expires_in etc. in an object. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ 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/
