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.

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

Upgrade to v3 of the jwt-go dependacy #8

Merged
merged 1 commit into from
Jul 19, 2016

Conversation

namsral
Copy link
Contributor

@namsral namsral commented Jul 11, 2016

  • Add jwt.MapClaims type assertion to fix missing indexing support for
    type jwt.Claims

Followed migration guide at:
https://github.com/dgrijalva/jwt-go/blob/master/MIGRATION_GUIDE.md

- Add jwt.MapClaims type assertion to fix missing indexing support for
  type jwt.Claims

Followed migration guide at:
https://github.com/dgrijalva/jwt-go/blob/master/MIGRATION_GUIDE.md
@BTBurke
Copy link
Owner

BTBurke commented Jul 11, 2016

Awesome thanks. I'll merge this in tomorrow.

On Jul 11, 2016, at 11:04 PM, Lars Wiegman notifications@github.com wrote:

Add jwt.MapClaims type assertion to fix missing indexing support for type jwt.Claims
Followed migration guide at:
https://github.com/dgrijalva/jwt-go/blob/master/MIGRATION_GUIDE.md

You can view, comment on, or merge this pull request online at:

#8

Commit Summary

Upgrade to v3 of the jwt-go dependacy
File Changes

M jwt.go (11)
M jwt_test.go (24)
Patch Links:

https://github.com/BTBurke/caddy-jwt/pull/8.patch
https://github.com/BTBurke/caddy-jwt/pull/8.diff

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@BTBurke BTBurke merged commit adecc35 into BTBurke:master Jul 19, 2016
@BTBurke
Copy link
Owner

BTBurke commented Jul 19, 2016

@namsral Thanks for this. Sorry it took me so long to get this merged in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants