Remove duplicate session timeout system from Redis records

FixSecurityService
Shipped
March 9, 2026 at 10:16 PM UTC
Author
Kamo
Commit
f15afb5

Session expiry is now managed solely by the Redis key TTL. The internal createdAt/expiresIn fields stored inside the Redis value have been removed — they formed a second, stale timeout system that diverged from the actual TTL after sliding expiration refreshed it. - createSession: no longer stores createdAt or expiresIn in the record - getSessionInfo: removed tokenExpiration calculation from internal fields - extendSession: replaced read-modify-write with a single expire() call - getUserInfo (SecurityController): expiration/expiresIn now derived from actual Redis TTL via getSessionTTL() instead of internal hash fields

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing