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
If the "expires at" claim is set to a date larger than 2038-01-19, then it gets broken by the fact that the date is translated into a int. See PayloadSerializer line 58
The latest date possible to represent in seconds as a Java Integer is
new Date(Integer.MAX_VALUE * 1000L);
Which corresponds to 2038-01-19T04:14:07.000+0100
The date claims should always be respresented as Long in Java since the second values will overflow the Integer max value and you will get an erroneous value.
This applies to the other timestamp claims also (issued at, and not before) together with the custom date claims.
The text was updated successfully, but these errors were encountered:
If the "expires at" claim is set to a date larger than 2038-01-19, then it gets broken by the fact that the date is translated into a int. See PayloadSerializer line 58
The latest date possible to represent in seconds as a Java Integer is
new Date(Integer.MAX_VALUE * 1000L);
Which corresponds to 2038-01-19T04:14:07.000+0100
The date claims should always be respresented as Long in Java since the second values will overflow the Integer max value and you will get an erroneous value.
This applies to the other timestamp claims also (issued at, and not before) together with the custom date claims.
The text was updated successfully, but these errors were encountered: