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

Consider to migrate to a different jwt library #12475

Closed
mitake opened this issue Nov 15, 2020 · 3 comments · Fixed by #12580
Closed

Consider to migrate to a different jwt library #12475

mitake opened this issue Nov 15, 2020 · 3 comments · Fixed by #12580
Labels
area/auth type/feature

Comments

@mitake
Copy link
Contributor

mitake commented Nov 15, 2020

It seems that https://github.com/dgrijalva/jwt-go isn't maintained actively (according to dgrijalva/jwt-go#426). If we cannot expect important updates, we should consider to migrate to a different jwt library.
@goku321
Copy link

goku321 commented Nov 26, 2020

How about I try working on this?

@brumhard
Copy link

This is also addressed in #12580 and should be merged cause as of right now etcd contains this vulnerability reported by snyk.

@dlorenc
Copy link
Contributor

dlorenc commented Jan 13, 2021

Whoops, missed this issue. Yep, my PR should be ready for review.

@ptabor ptabor linked a pull request Jan 15, 2021 that will close this issue
Switch from dgrijalva/jwt-go to form3tech-oss/jwt-go. #12580
Merged
@padyx padyx mentioned this issue May 2, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/auth type/feature
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch from dgrijalva/jwt-go to form3tech-oss/jwt-go. dlorenc/etcd
5 participants
@mitake @dlorenc @spzala @goku321 @brumhard