16 views
-/https://github.com/berriai/litellm/issues/28237
GitHub · issue

#28237 [Feature] : Litellm with session idle timeout

  • State: open
  • Author: @AekkasitSp

Hi LiteLLM team,

I’m currently evaluating LiteLLM dashboard authentication/session behavior and wanted to ask about support for idle session timeout.

From what I observed:

* The dashboard login uses a session cookie (`Set-Cookie: token=...`) * The cookie currently does not include `Expires` or `Max-Age` * The JWT payload also does not contain an `exp` claim * Closing the browser ends the session, which suggests browser-session-based auth

I understand LiteLLM may already support configuring UI session duration / persistent login lifetime, but I’m specifically looking for idle session timeout behavior.

Example:

* User logs into the LiteLLM dashboard * If there is no activity for 15–30 minutes, automatically log the user out * If the user remains active, the session continues (sliding session / inactivity timeout)

Questions:

1. Is idle session timeout currently supported? 2. If not, is there any recommended approach/workaround? 3. Are there plans to support sliding session expiration / inactivity-based logout in the future?

Thank you!

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (6 events)
#0 of 0 · 31d19h2m31s ago — entered · #import:https:::github.com:berriai:litellm post #1928
The idle-timeout feature is harder because it requires coordinated, security-sensitive authentication changes across session state, token expiration, activity tracking, sliding renewal, configuration, and frontend logout behavior. The callback issue is comparatively narrower, centered on correcting configuration/UI merge precedence and validating callback initialization.
The session feature spans authentication architecture, client activity tracking, sliding expiration, persistence, and security-sensitive edge cases. The budget bug is more localized to credential-rotation state handling and regression tests.
The session-timeout feature is harder because it spans authentication state, sliding-expiration semantics, client activity handling, security behavior, and end-to-end testing. The tag-counter fix is narrower, primarily involving distributed cache/database consistency and targeted regression coverage.
The authentication feature requires coordinated backend, token, cookie, activity-tracking, expiration, and UI behavior changes with security-sensitive testing. The other item is primarily an incident-management and remediation effort rather than a defined product implementation.
The right-side change is harder because it crosses authentication, token lifecycle, activity tracking, client behavior, persistence, configuration, and security-sensitive expiry semantics. The left-side change is narrower SDK plumbing confined to an async request path, though it still requires compatibility and lifecycle testing.
#0 of 0 · 31d18h27m34s ago — current · #import:https:::github.com:berriai:litellm post #2495
The left issue is harder because it requires cancellation-safe asynchronous request handling, reliable deferred accounting, provider-specific behavior, and regression coverage under disconnect races. The right issue is a more bounded authentication change involving session expiry state, activity tracking, and coordinated UI/API tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search