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

Better handle indications that the auth token may have expired #594

Open
phantomjinx opened this issue Jan 9, 2025 · 0 comments
Open

Better handle indications that the auth token may have expired #594

phantomjinx opened this issue Jan 9, 2025 · 0 comments

Comments

@phantomjinx
Copy link
Member

Logging in with a token, especially when using form authentication, requires entering a token that may have been generated using create token <service-account>. Such tokens can have quite short lifetimes hence expire. However, expiration is not necessarily tested when authenticating and the token may actually expire after logging-in. Such a use-case results in no pods being displayed in Discover due to error 401 responses being returned from requests to the cluster API server.

Better information informing the user with some kind of warning that the token may need renewing (if not renewing automatically) would be beneficial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant