Vincent Prouillet
Vincent Prouillet
I'm not planning to add that, it seems to be a German only thing?
I'm not sure why this error happens but that would be an invalid JWT either way. We should have a better error though but it looks like it comes from...
It's only used internally, I didn't think anyone needed that?
Ah the docs should be updated.
That or `Validation::new(Algorithm::..)` with the alg you are using
Maybe our pem decoder (https://github.com/Keats/jsonwebtoken/blob/master/src/pem/decoder.rs) doesn't work well in some cases? I don't know, I haven't touched that part in years
I'm not sure it makes sense. It's added to DecodingKey because you commonly get them as components (eg JWKs). It's much rarer for the encoding part.
1. I don't see why we would go to ms resolution when we only have seconds in the api/sec 2. Not an issue with a decent leeway, that's what it's...
It seems that what you want, rather than negative leeway which is imo a bit confusing is another option to reject tokens that are `x` seconds or less from expiration?
Something like `Validation::reject_tokens_expiring_in_less_than(seconds: int)`?