[Cherry-pick to branch-1.3] [#12588] improvement(web2-ui): Expose UI session timeout settings through server configuration (#12621) - #12780
Merged
Conversation
…ough server configuration (#12621) ### What changes were proposed in this pull request? - Added three optional server-side UI session timeout configurations: - gravitino.ui.sessionIdleTimeoutMs - gravitino.ui.sessionMaxDurationMs - gravitino.ui.sessionIdleWarningLeadMs - Added the configurations to conf/gravitino.conf.template with commented defaults and descriptions. - Updated the UI to resolve values in this order: 1. /configs API 2. Corresponding NEXT_PUBLIC_* environment variable 3. Built-in default value - Removed gravitino.authorization.serviceAdmins from visibleConfigs; it is already exposed automatically by the /configs API when authorization is enabled. ### Why are the changes needed? Session timeout behavior previously depended only on UI environment variables and hardcoded defaults. This made deployment-specific configuration inconvenient and required rebuilding or separately configuring the UI. The server configuration now provides a centralized way to configure idle timeout, maximum session duration, and warning lead time. Fix: #12588 ### Does this PR introduce any user-facing change? Yes. - Adds three optional server configuration keys for UI session management. - Existing UI environment variables and defaults remain supported as fallbacks. - gravitino.authorization.serviceAdmins remains available through /configs when authorization is enabled; it no longer needs to be listed in gravitino.server.visibleConfigs. - No public REST API shape or authentication API changes are introduced. ### How was this patch tested? From web-v2/web: pnpm test pnpm lint
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cherry-pick Information:
branch-1.3