https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38338
--- Comment #21 from David Cook <[email protected]> --- (In reply to Thomas Klausner from comment #18) > * First step: Add XOAUTH support to the Koha SMTP sender > * all the hard parts are already available on CPAN: LWP::Authen::OAuth2, > Authen::SASL::Perl::XOAUTH2 and Email::Sender > * we "just" need to add some new config settings to SMTP to allow using an > access-token (instead of username/password) > * we will also need to set up a cronjob to refresh the access tokens and > the refresh token (better via cronjob, because if the mail sending happens > infrequently even the refresh token could be invalidated in the interval > where nothing happend) > * The XOAUTH setup (i.e. the OAuth handshake to login the service account > and create a first refresh token) will be done via a command line script > * Second step (optional): > * Add a GUI to the Staff interface to setup XOAUTH and do the OAuth > handshake (so system librarians can do the setup without needing access to > the shell) > * Probably do this via a plugin In theory, I think that this all sounds good to me. That said, I haven't tried the XOAUTH setup before, so that's the thing that I still need to wrap my head around. Still just looking around on Google at how to get the initial access token. I find the run throughs like https://github.com/google/gmail-oauth2-tools/wiki/OAuth2DotPyRunThrough to be interesting because they use the "Installed application" type and not the "service account" type, but surely we'd want to use service accounts. Anyway, it's just this process that I still need to spend some time on... -- 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] 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/
