yezhenghao opened a new pull request, #11502: URL: https://github.com/apache/apisix/pull/11502
…ilar to the jwt-auth plugin, which belongs to the permission authentication plugin. The difference is that for cwt plugin, apisix uses the chain wallet address in the consumer whitelist configuration, does not touch the key, the key only belongs to the client user, which is a decentralized mode, while jwt-auth plugin needs to configure the key in the consumer of the apisix to generate the token. It's a centralized model. The cwt plugin can be used in scenarios where mutual trust is required or where it is not convenient to expose the key. ### Description <!-- Please include a summary of the change and which issue is fixed. --> <!-- Please also include relevant motivation and context. --> Fixes # (issue) ### Checklist - [ ] I have explained the need for this PR and the problem it solves - [ ] I have explained the changes or the new features added to this PR - [ ] I have added tests corresponding to this change - [ ] I have updated the documentation to reflect this change - [ ] I have verified that this change is backward compatible (If not, please discuss on the [APISIX mailing list](https://github.com/apache/apisix/tree/master#community) first) <!-- Note 1. Mark the PR as draft until it's ready to be reviewed. 2. Always add/update tests for any changes unless you have a good reason. 3. Always update the documentation to reflect the changes made in the PR. 4. Make a new commit to resolve conversations instead of `push -f`. 5. To resolve merge conflicts, merge master instead of rebasing. 6. Use "request review" to notify the reviewer after making changes. 7. Only a reviewer can mark a conversation as resolved. --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
