Katalyst: Frequent session timeouts while users are actively working

Description

• Users are logged out or see session timeout messages even while actively working in Katalyst.
• They must repeatedly log back in, causing workflow disruption.
• Timeouts may be caused by application session settings, proxy/SSO timeouts, or idle detection issues.

Solution

• Determine which component enforces session timeout:
  • Katalyst application session (server config).
  • Reverse proxy/load balancer idle timeout.
  • SSO/IdP session or token lifetime.
• Adjust timeouts:
  • Set Katalyst session timeout to a value aligned with security policy but practical (e.g., 60+ minutes for active sessions).
  • Increase proxy idle/keep‑alive timeouts so normal operations aren’t interpreted as idle.
  • Coordinate with security teams if SSO token lifetimes need adjustment.
• Prevent double‑timeouts:
  • Ensure SSO and Katalyst session durations are aligned—do not set one much shorter than the other.