-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
-
0.38
The plugin caches (https://github.com/jenkinsci/github-oauth-plugin/pull/100) some user's information for a period of time.
If Github is using SSO for a specific organization, it's possible that user authenticates with Github but has an expired SSO. In such a scenario, the plugin will not be able to receive the list of teams under this organization. This information is then cached for one hour.
If the teams are being used in managing permissions, the users will effectively lose all these permissions during this period of time without any way of fixing it (except for restarting jenkins).
I hope there can be a way to better manage this cache (option to control the cache time, etc.). Better, if it's possible, to refresh the cache if the user is trying to perform a reauthentication.
This is a huge problem for my team. Multiple times per week I end up penalized for an hour because I didn't realize it had been too long since I reloaded my company SSO page and then reloaded our GitHub org page before attempting to use Jenkins. Anything we can do to get movement on this?