Fix ComponentVerifyTicket Redis cache expiration from infinite to 12 hours #3719
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
The
ComponentVerifyTicket
in Redis-based configuration storage classes was being cached withInteger.MAX_VALUE
expiration time (essentially infinite), which contradicts WeChat's official documentation stating thatcomponent_verify_ticket
has a validity period of 12 hours.This could lead to:
Solution
Updated the expiration time in
setComponentVerifyTicket()
method fromInteger.MAX_VALUE
to43200
seconds (12 hours) across all Redis-based configuration storage implementations:Before:
After:
Files Changed
WxOpenInRedissonConfigStorage.java
WxOpenInRedisConfigStorage.java
WxOpenInRedisTemplateConfigStorage.java
References
Testing
This change aligns the cache behavior with WeChat's official specifications and ensures proper token lifecycle management.
Fixes #3683
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.