Dave Grijalva

Please try `go get github.com/dgrijalva/jwt-go/v4@a58974ee87a68abcf6cfb2315224e89135cf3311` and let me know if that works

Hi! Sorry for the delay. It looks like we're moving in the direction of https://github.com/golang-jwt/jwt? I have no real preference other than wanting to be careful not to break things...

There seems to be a few different approaches still on the table here. Can we get to a consensus on: - who's going to raise their hand to be a...

I've updated the README to reflect the new location. Per @mfridman's suggestion, if someone wants to help coordinate a final release for this repo, I can review and land it...

Thanks for this. This looks like a backwards incompatible change. I need to look into this a little bit to ensure we don't violate semver, but it looks like it's...

Issued at checking will be removed in v4, per the jwt spec.

Simplest workaround is probably to wrap your claims type in something custom that bypasses the IAT check. Here's a lazy example I didn't actually test. Something like the following should...

`jwt.Claims` is an interface. The claims value you pass into the parser needs to be a concrete type. It's essentially passed directly through to the standard library JSON parser and...

How will a `MapClaims` object be created that has int values? The reason we look at `json.Number` and `float64` is that those are the two possible types returned from the...

Sorry for the delay. I've been on vacation. @johnlockwood-wf I don't understand your question about the example test.