-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
jenkins : 2.414.1
github oauth plugin : 588.vf696a_350572a_
-
-
596.v0646c4a_0a_962
When connecting to Jenkins using GitHub OAuth, there is a significant delay before information about the groups to which the user belongs comes back down.
We can make sure by consulting the whoAmI page.
There may be a wait of up to 1 minute before the information is actually sent down.
2 problems arise from this :
- Links from /static-files/ return a 403 exception (same as JENKINS-63296)
- Build launches generate a "could not be located" exception (same as JENKINS-67026)
This is extremely penalizing for us
- causes
-
-
- Closed
-
- is related to
-
-
- Open
-
- links to
[JENKINS-72209] Authorities are not immediately returned from github when login
cpottiers could you check the most recent release and confirm that the issue is resolved?
Hi markewaite, wfollonier ,
At first sight it's OK because icons , links are accessibles and jobs are runnables.
cpottiers I'm sorry to share that the change was reverted from the plugin in the next release because it caused an unexpected performance impact on Pipeline execution. More research is needed before the change can be introduced again.
cpottiers if you are using the version with the fix and do NOT see the performance issue, please tell us as well 
wfollonier we use a self hosted instance (github entreprise edition 3.10.2) and we don't see for the moment any performance issue (with 596.v0646c4a_0a_962 version).
markewaite yes but it's a closed issue, how can I see any evolution about this point ?
I would expect further changes will be discussed in this issue or in a pull request that is linked to this issue. cpottiers
Sorry cpottiers no time to spend on this issue recently (and for the foreseeable future unfortunately)
cpottiers Potentially the issues you were seeing are corrected by https://github.com/jenkinsci/github-oauth-plugin/pull/256. As it's related to a cache issue that seems related to JENKINS-72268.