jsonwebtoken/jsonwebtoken.github.io

NumericDates are in Milliseconds, not Seconds as defined in RFC 7519

Closed this issue · 1 comments

Hello,

I don't know, whether this is an issue with jwt.io itself or an included library, please apologise, if I'm opening this issue in the wrong repository.

[RFC 7519] states, that the claims iat, nbf and exp "MUST be a number containing a NumericDate value". NumericDate is defined as "[...] the number of seconds from 1970-01-01T00:00:00Z [...]" - see last definition in Terminology.

The site jwt.io uses milliseconds.

I could imagine, that this is an easy to make mistake. So additionally to fixing it on jwt.io it might be useful, to see a hint for each referenced library, indicating whether it is conforming to the spec or not.

No, the error is with me and using java.util.Date correctly :-/, closing this issue