-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenIDConnectionUtils#persistKubeConfigWithUpdatedToken persists access token instead of refresh token #2783
Closed
oliviaKar opened this issue
Feb 3, 2021
· 2 comments
· Fixed by #2869 or jenkinsci/kubernetes-client-api-plugin#83
Closed
OpenIDConnectionUtils#persistKubeConfigWithUpdatedToken persists access token instead of refresh token #2783
oliviaKar opened this issue
Feb 3, 2021
· 2 comments
· Fixed by #2869 or jenkinsci/kubernetes-client-api-plugin#83
Comments
@oliviaKar : Thanks a lot for reporting this. Could you please raise a quick PR to fix this? |
@oliviaKar : Hi, Which cloud provider are you using? |
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Mar 3, 2021
…dToken persists access token instead of refresh token
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Mar 4, 2021
…dToken persists access token instead of refresh token
11 tasks
manusa
pushed a commit
that referenced
this issue
Mar 5, 2021
…rsists access token instead of refresh token
This was referenced Mar 12, 2021
This was referenced Mar 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/fabric8io/kubernetes-client/blob/master/kubernetes-client/src/main/java/io/fabric8/kubernetes/client/utils/OpenIDConnectionUtils.java#L263
Here it seems like the access_token is retrieved from the updated config and persisted as the refresh token.
The behaviour that we have observed is that the config gets refreshed once, but cannot keep getting refreshed as the persisted refresh-token is not valid.
The text was updated successfully, but these errors were encountered: