https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38338
--- Comment #20 from David Cook <[email protected]> --- (In reply to Tomás Cohen Arazi (tcohen) from comment #19) > The token should be retrieved (if a refresh is needed) when it's going to be > used. I don't think we need a cronjob here. > > Making the API call to retrieve a fresh token, if it has expired or absent, > could be done during the sending session. Theoretically yes but in practice if you're a system that rarely sends emails your refresh token might expire before you have a chance to send another email, and then your email authentication is broken until someone can re-configure it. That's why a cronjob can help keep your refresh token refreshing in the background, so that it's never expired. It's not quite clear how long refresh tokens live for major providers. I think it's 90 days for Microsoft, but no idea for Google. > Excited someone can devote time to accomplish this. Agreed. Or rather... excited that multiple people are interested in this topic and willing to move forward on it. -- 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/
