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.

Sign up for GitHub

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

Jump to bottom

feat: Add the cwt(chain web token) plugin. #11502

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

feat: Add the cwt(chain web token) plugin. #11502

wants to merge 1 commit into from
+1,635 −0

Conversation

yezhenghao
Copy link

…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

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 first)

feat: Add the cwt(chain web token) plugin. The target function is sim…
3acd41d 
…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.
@dosubot dosubot bot added size:XXL This PR changes 1000+ lines, ignoring generated files. enhancement New feature or request plugin labels Aug 16, 2024
@shreemaan-abhishek
Copy link
Contributor

please create an issue with the proposal describing "why" first, then "how" and then "what".

@shreemaan-abhishek
Copy link
Contributor

also, please fix the PR title. It looks horrific right now.

@yezhenghao yezhenghao changed the title feat: Add the cwt(chain web token) plugin. The target function is similar 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. feat: Add the cwt(chain web token) plugin. Aug 30, 2024
@yezhenghao
Copy link
Author

yezhenghao commented Aug 30, 2024 •
edited
Loading

please create an issue with the proposal describing "why" first, then "how" and then "what".

an issue was created. #11542

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
enhancement New feature or request plugin size:XXL This PR changes 1000+ lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@yezhenghao @shreemaan-abhishek