针对企业微信第三方应用开发获取各种token和ticket时新增了基于redission并发锁的版本 - #2000
Merged
Merged
Conversation
ibootz
commented
Feb 13, 2021
- 获取suiteAccessToken,corpAccessToken,providerToken,authCorpJsapiTicket,suiteJsapiTicket时,支持采用分布式锁的方式来锁定获取过程,防止出现微服务中常见的多进程覆盖问题
- 新增机构级jsapiTicket签名方法和应用套件级的jsapiTicket签名
- 纠正了几个之前存在的bug
- 添加了必要的单元测试
1. 获取suiteAccessToken,corpAccessToken,providerToken,authCorpJsapiTicket,suiteJsapiTicket时,支持采用分布式锁的方式来锁定获取过程,防止出现微服务中常见的多进程覆盖问题 2. 新增机构级jsapiTicket签名方法和应用套件级的jsapiTicket签名 3. 纠正了几个之前存在的bug
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.