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

Consider upgrading to jwt-go 3.0.0 #76

Closed
leetal opened this issue Aug 21, 2016 · 1 comment
Closed

Consider upgrading to jwt-go 3.0.0 #76

leetal opened this issue Aug 21, 2016 · 1 comment
Labels
feat New feature or request.

Comments

@leetal
Copy link
Contributor

leetal commented Aug 21, 2016

Hi Aeneas!

So, i'm still following the development of all your libraries and we've just now started to implement our interfaces against fosite/hydra. It came to a quick halt when we realized that fosite relies upon v2.7.0 of jwt-go, and that we must use 3.0.0 of jwt-go. We also use glide and this is causing a clash since jwt-go have introduced a breaking change by replacing the map[string]interface{} to a jwt.Claims interface (essentially exactly like your jwt_claims.go).

Do you want help fixing this change (more or less just upgrade to 3.0.0 of jwt-go and create a new type that implements the Claims interface in fosite) or is this on your backlog?

Regards
Alexander W

@aeneasr
Copy link
Member

aeneasr commented Aug 21, 2016

@leetal yes, I welcome if you could help me with upgrading to 3.0. This has been a pain ever since they broke bc. :)

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

No branches or pull requests

2 participants