https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38338
--- Comment #2 from David Cook <[email protected]> --- With the "sasl-xoauth2" plugin, I believe that it handles auto-refreshing of the access token, so while there is a bit of overhead for the backend sysadmin at first, once it's set up, it should be fairly set and forget. (Although if your refresh token expires, then you'll need to set it up again.) -- Now I also mentioned "cyrus-sasl-xoauth2". I don't understand it as well and its documentation is not very good at all. However, my understanding is that you have to pass the access_token value directly as the sasl_password. That means no auto-refreshing of access tokens or anything like that. If we were to support that SASL plugin, then we'd have to handle a lot of the OAuth2 process ourselves, which is not impossible, but it would involve significantly more work. So... at the moment I'm inclined to go with "sasl-xoauth2". -- Additionally, on the "perl-authen-sasl" github by "gbarr", I raised an issue called "Supporting XOAUTH2 authentication?", and there I think the repo maintainer would be open to accepting a patch for a pure Perl XOAUTH2 implementation. I don't know that any of us have the time/expertise to do that, but that's a opportunity open to folks as well. (We could also instantiate our own Authen::SASL plugin and pass that to Email::Sender::Transport::SMTP::Persistent using sasl_authenticator.) -- 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/
