You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The token obtained through the REST API is new each time and has the configured expiration duration. However, I noticed that Redis uses a hash data structure for storage, which seems to cause the subsequent tokens obtained by the same user to not reach the expected full expiration duration (configured expiration duration). Instead, they may expire prematurely along with the hash key.
Screenshots Link
The text was updated successfully, but these errors were encountered:
kubbot
changed the title
[BUG] rest api的获取token似乎并不能达到预期的过期时间
[BUG] The rest api's token acquisition does not seem to meet the expected expiration time
Jul 6, 2024
OpenIM Server Version
3.7.1
Operating System and CPU Architecture
Linux (AMD)
Deployment Method
Source Code Deployment
Bug Description and Steps to Reproduce
The token obtained through the REST API is new each time and has the configured expiration duration. However, I noticed that Redis uses a hash data structure for storage, which seems to cause the subsequent tokens obtained by the same user to not reach the expected full expiration duration (configured expiration duration). Instead, they may expire prematurely along with the hash key.
Screenshots Link
The text was updated successfully, but these errors were encountered: