Support an option for leeway when validating with JwtTime about jwt-scala HOT 3 CLOSED

Added in 0.7.1

from jwt-scala.

As always, trying to figure a solution with the current API before adding new stuff. Is there a difference between adding 1min leeway compared to adding 1min to your session duration? As I see it in the spec, this leeway is implementation specific and internal, not accessible to users.

from jwt-scala.

I only saw brief mention of this in the spec in 2 places. For servers, my assumption is that the clocks will be very close. I'm allowing some leeway to account for client clock skew so that clients can eagerly renew their sessions to save a round trip in getting a rejected request. My tokens also happen to be issued by another app service, however I could definitely change the expiration there.

I'd say this would be a nice to have but no means not a deal breaker. If added I think it would be an optional thing as I could say many people wanting exact time validation.

from jwt-scala.