Add leeway for expiration of cached DAT about ids-messaging-services HOT 1 CLOSED

There is a way that does not depend on the validity period of the DAT.
Straight from the JWT RFC:

The "exp" (expiration time) claim identifies the expiration time on
or after which the JWT MUST NOT be accepted for processing. The
processing of the "exp" claim requires that the current date/time
MUST be before the expiration date/time listed in the "exp" claim.
Implementers MAY provide for some small leeway, usually no more than
a few minutes, to account for clock skew. Its value MUST be a number
containing a NumericDate value. Use of this claim is OPTIONAL.

As a side effect, this should also cover the edge cases you are talking about :)

from ids-messaging-services.