KamoCRM

Remove duplicate session timeout system from Redis records

FixSecurityService
Ya
9 Machi 2026, 22:16 UTC
Mwandishi
Kamo
Ahadi ya
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

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei