Update version of jwt-go

[mgkeen]

Don't know if you want to use this or not. I've updated the version of jwt-go to the latest. I was having dependency clashes in my project so needed it to reference latest jwt-go.

The biggest change was that claims was no longer a map[string]interface{}, so had to use the MapClaims type provided.

There was also a change in the way it validates expiry time, essentially treating a 0 value as if the claim wasn't specified. The test was previously using a zero value to test for a failed expiry, so i have adjusted that to pass up a value of 1 instead.

[StephanDollberg]

Hi @mgkeen ,

Thanks for the PR. This looks pretty great and I will definitely get started based on this.

However, if you have a look at the other open PRs, I want to integrate some breaking changes into the refactoring to v3 and consequently won't merge this as is.

Thanks again,
Stephan

[hyacinthus]

So seven months have gone...

[StephanDollberg]

Hi, yeah I am sorry. This doesn't have my first priority and I am kinda busy at work right now. Like I said, I also don't want to rush it and consider additional options once we break the API. Cheers, Stephan

…

On Feb 8, 2017 9:02 AM, "王瑞华" ***@***.***> wrote: So seven months have gone... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#18 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACxSk-zJPdElHGbUlsChD4E7Za25FiWkks5raYS7gaJpZM4JVYRP> .