Exp verification fails for dates in the far future about jwt-cpp HOT 2 CLOSED

Hi and thank you for checking such extreme cases.
I did some checking and found the exact date it will fail:
04/11/2262 @ 11:47pm (UTC)

What your hitting is the maximum value of a 64bit long (9223372036).
jwt-cpp uses a std::chrono::system_clock::time_point to store time and date information.
At least on my system (and I guess most) this is a typedef to std::chrono::time_point<std::chrono::_V2::system_clock, std::chrono::duration<long, std::ratio<1l, 1000000000l> > >, i.e. the time_t value in nanoseconds.

Is this a real problem for your application or just a theoretical one?

EDIT: I think the reason why there is so little documentation about those limits is that it is not defined in the C++ spec. Why it does not fail on windows is most likely because it uses a less accurate unit in its implementation. If you use micro or milliseconds, it will postpone your problem by a couple of thousand years.
That said, I doubt any system we build will still be around in 2250 and I'm 100% sure they won't blame you when it finally fails.

from jwt-cpp.

Thanks for the quick response and guidance. Its really just a theoretical one, we just have a JWT for convenience with such a long expiration time. It's kind of a shame these limits aren't more documented, but I suppose since its implementation specific it would be kind of hard.

Thanks again!

from jwt-cpp.