https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38338
Michał <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |om --- Comment #5 from Michał <[email protected]> --- For auto-refresh, there's also a challenge in that the refreshed credentials will have to be retrieved and saved back to the database (unless you say it's specifically filepath as password, and then the library would just write to that file instead on its own, then that'd be covered already I suppose). There's also the open question about whether Koha should offer some kind of way in the interface to open up login page for some common providers (or a configurable custom one). If yes, then whether it should provide some kind of default community OAuth app client ID to make it easiest (I vote yes, apps like Thunderbird do just that) (of course these app IDs could and should be made configurable to allow flexibility there if need be). I imagine someone could click a button to add server, choose a preconfigured provider like Google Mail or Microsoft, be directed to login page, after login the new server with all data would be populated, easy. Similarly an existing server with oauth login specified should have an option to trigger a login and generation of new access+refresh token data afresh as well. -- 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/
