-
Bug
-
Resolution: Done
-
Major
-
1.14.1.Final
-
None
JwtValidator is reading the exp and nbf field as a Java int instead of long:
This means the maximum expiration date is ~January 18, 2038. Also, with Javascript a NumericDate this would be a 64-bit value. The JWT spec also leaves open the possibility of a decimal value so that should possibly be accounted for.
- is cloned by
-
JBEAP-20939 (7.3.z) ELY-2069 - JWT token validation uses int instead of long for the dates: exp (expiration) and nbf
- Closed