Skip to content
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

refresh id tokens for auth-providers #72

Closed
clux opened this issue Sep 17, 2019 · 0 comments · Fixed by #234
Closed

refresh id tokens for auth-providers #72

clux opened this issue Sep 17, 2019 · 0 comments · Fixed by #234
Labels
config Kube config related help wanted Not immediately prioritised, please help!

Comments

@clux
Copy link
Member

clux commented Sep 17, 2019

addon for #70 to be able to refresh auth nicely in a stand-alone binary when using oidc providers.

id-token requires a dependency to jsonwebtoken and maybe to be able to update kubeconfig.

a work-around in the mean time is probably to shell out to kubectl for this particular feature (or delete entries in the auth-provider).

@clux clux added help wanted Not immediately prioritised, please help! config Kube config related labels Sep 17, 2019
thomastaylor312 added a commit to thomastaylor312/kube-rs that referenced this issue Apr 21, 2020
This is by no means elegant, but seems to be functional. Setting the
authorization headers now occurs at request time instead of during
initial configuration. It will only try to refresh a token if the
configured expiration time has passed.

Closes kube-rs#72
thomastaylor312 added a commit to thomastaylor312/kube-rs that referenced this issue Apr 23, 2020
This is by no means elegant, but seems to be functional. Setting the
authorization headers now occurs at request time instead of during
initial configuration. It will only try to refresh a token if the
configured expiration time has passed.

Closes kube-rs#72
thomastaylor312 added a commit to thomastaylor312/kube-rs that referenced this issue Apr 24, 2020
This is by no means elegant, but seems to be functional. Setting the
authorization headers now occurs at request time instead of during
initial configuration. It will only try to refresh a token if the
configured expiration time has passed.

Closes kube-rs#72
thomastaylor312 added a commit to thomastaylor312/kube-rs that referenced this issue Apr 27, 2020
This is by no means elegant, but seems to be functional. Setting the
authorization headers now occurs at request time instead of during
initial configuration. It will only try to refresh a token if the
configured expiration time has passed.

Closes kube-rs#72
@clux clux closed this as completed in #234 Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
config Kube config related help wanted Not immediately prioritised, please help!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant