-
Notifications
You must be signed in to change notification settings - Fork 98
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
interactive
mode results in an empty refresh_token
#499
Comments
Token caching is only supported in v1.8.0-beta |
I think azidentity sdk 1.8.0 was released yesterday: And there is already a dependabot pull request :-) |
cool. I will take a look next week. I actually re-wrote almost everything in https://github.com/weinong/kubelogin/tree/feat/token-cache with preview sdk. If you want to test, go for it! I need to add tests. |
@weinong hey, i tested the solution from the branch you are linking, and it looks good... The cache file is created, and credentials including refresh token are stored in keychain (in case of MacOS).
any chance that the suggested changes can be merged and released? |
As described here in #311 it looks like
interactive
login mode is not getting arefresh token
, so reauth is required every ~70 minutes (validity of AAD access token). It looks like all the upstream issues mentioned in the original issue #311 in azure go sdk are closed/implemented.Using
interactive
is IMO more user-friendly and should support caching of therefresh token
in a similar way to howdevicecode
works.The text was updated successfully, but these errors were encountered: