Play request.jwtSession can't deserialize when using a non-empty claim about jwt-scala HOT 2 CLOSED

You are not missing anything. This was a design choice but to be honest, I'm still not sure if it was the best one.

The idea is that you will always be able to extract a JwtSession from the request. If it is valid, it will have all the data inside it. If it is invalid, it will be an empty session (no claim mostly). Since your token is expired regarding the exp value, you get an empty session. In this particular use case, the lib does not care why it is invalid, as long as it's not good, it considers it an empty session.

Try again with an exp far away in the future and it should work just fine.

from jwt-scala.

Thanks for the reply. This design choice suits me well.

My issue is in fact related to “how is 'exp' implemented" and not about claim implementation.

Thanks for the explaination

from jwt-scala.