- Dikirim
- 9 Maret 2026 pukul 22.16 UTC
- Penulis
- Kamo
- Berkomitmen
- 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