Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] The rest api's token acquisition does not seem to meet the expected expiration time #2399

Closed
7FreezingPoint opened this issue Jul 6, 2024 · 1 comment · Fixed by #2403
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@7FreezingPoint
Copy link

7FreezingPoint commented 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

eb92fcd5cf0446b3b811926537dd7b9

@7FreezingPoint 7FreezingPoint added the bug Categorizes issue or PR as related to a bug. label Jul 6, 2024
@kubbot 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
@icey-yu icey-yu mentioned this issue Jul 9, 2024
@icey-yu
Copy link
Member

icey-yu commented Jul 9, 2024

The issue has been fixed. Thank you for pointing it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants