-
Notifications
You must be signed in to change notification settings - Fork 394
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.
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
Update to golang-jwt V5 #332
base: master
Are you sure you want to change the base?
Conversation
The error types that were being used were removed in v5
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #332 +/- ##
==========================================
+ Coverage 87.36% 88.76% +1.40%
==========================================
Files 1 1
Lines 459 454 -5
==========================================
+ Hits 401 403 +2
+ Misses 45 38 -7
Partials 13 13
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
if claims["exp"] == nil { | ||
mw.unauthorized(c, http.StatusBadRequest, mw.HTTPStatusMessageFunc(ErrMissingExpField, c)) | ||
return |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sure if this should be kept, or if the WithExpirationRequired
should just always be added similar to how I added WithTimeFunc
.
Added test case for using the expiration required parser option
Updates the golang-jwt/jwt dependency to V5
Updates an error check in the middleware due to expanded validation in V5
Modifies a check in the refresh flow due to the reworking of errors in V5
Let me know if additional changes need to be made, or if I missed anything in the contribution process.
Thanks!