You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like there should be consistency between the different JWT gems/packages. The node package will generate an iat by default, while this gem does not.
I always thought of the standard as trying to make the token as small as possible by default. The claims are left for per-case basis and their usefullness highly depends on each partocilar use case.
The majority of my use cases didn't need to know the age or creation time of the token (iat) but the expiration time (some tokens were just exp value with a signature).
I personally don't like the idea to deviate from the standard just because other did that. Though it's up to the maintainers of the gem.
I have the urge to close this issue. I feel that the library should not take any decisions on behalf of the users and assume everyone wants something optional.
Seems like there should be consistency between the different JWT gems/packages. The node package will generate an
iat
by default, while this gem does not.From node-jsonwebtoken
The text was updated successfully, but these errors were encountered: