Respect WebIdleTimeout in bearerTokenTTL #59645
Draft
+78
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The webUI will log a user out due to invalid token if they haven't pinged the server within the idle time, which defaulted to the bearer token default (10 minutes). Instead, we should only default to 10 minutes if the web_idle_timeout is not configured in the cluster config. this aligns with how it is described in the documentation.
docs reference: https://goteleport.com/docs/connect-your-client/web-ui/
changelog: Fix the webUI timeout time to respect the cluster's WebIdleTimeout configuration.
edit: moving to draft. im doing to see if there is a different mechanism that we can leverage for the same effect, without increasing the bearer token expiry