-
-
Notifications
You must be signed in to change notification settings - Fork 332
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
Bug/credentials id token #70
Conversation
Thanks a lot. This certainly looks sensible. Will try it out against my normal clusters. |
All seems fine here. Will add to the next release. Thanks again! |
Thanks, I guess supporting refresh of id-token requires a dependency to jsonwebtoken and maybe to be able to update kubeconfig. |
Ah that's why this stuff is always broken everywhere. Even with main |
Should be fine to pull that in though, doesn't look like it pulls in too many deps. Especially if we're trying to move to rustls long term #66. Happy to take a PR for it if it's somewhat maintainable. 🙂 |
maybe because some provider also update the refresh token, when you update the access-token (in fact allowing a refresh-token to be re-use is a security issue, iirc RFC) |
I'll be busy during the next 2 or 3 weeks, but I'll take a look after if I don't forgot. If my k8s user use the cli I made with kube-rs, I things they will complain about this randow error message about invalid token ;-). |
Ok, I've made #72 to track it at least. I'd appreciate the help when you have time! |
Do you have an ETA for 0.17.0 ? FYI my crate is a kubectl plugin: kubectl-view-allocations and output thing like:
Thanks |
You can always pin to a git sha in |
Released 0.17.0 now. |
Thanks, I release my crates: https://crates.io/crates/kubectl-view-allocations |
This basically restores the functionality that has been added in kube-rs#70. Same caveats apply here: auto-refresh of expired id-token is not supported.
This basically restores the functionality that has been added in kube-rs#70. Same caveats apply here: auto-refresh of expired id-token is not supported.
Our environment use OpenIDConnect (oidc) to setup some access to k8s (bare-metal).
Existing code failed because we have
auth-provider
but noaccess-token
and certificate use relative inside the .kube/config.This fix allow:
id-token
if presentauth-provider
is present butaccess-token
is absentCurrent, auto-refresh of expired id-token is not supported