https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38338
--- Comment #30 from David Cook <[email protected]> --- (In reply to David Cook from comment #28) > Ok, so I did a little sort of standalone proof-of-concept within > koha-testing-docker... As I speculated before, the tricky part is going to be fetching, storing, and refreshing the OAuth2 access token... Fetching probably won't be too hard, although I'm curious how different the different providers are... Keep in mind that the access token is often short-lived. With Gmail, it expires after 1 hour. It looks like their refresh tokens last about 7 days. Originally, I thought maybe we could separate the OAuth2 handling into a Koha plugin, but now... Koha's email code is probably going to need to have additional logic for handling access tokens and refresh tokens. For instance, if the token is expired, we'll probably want to pre-emptively refresh it (rather than trying to retry a failed email). We'll have to think about how to handle refreshing tokens on servers that send very few emails... (e.g. a nightly cronjob) -- 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/
