JWTProcessor always processes different token to churn out the same jwt id
Issue #369
invalid
Using version 8.19
It is simple to reproduce, just process any jwt and check the jwtid.. it will always return this value: "6a6d520d-1a93-4a44-81b8-38eb62442dd9" as the jwtid even though when decoded here [https://jwt.io/] it has a different jti.
Comments (2)
-
-
- changed status to invalid
That's alright, marking the ticket as invalid.
- Log in to comment
I am so sorry, please delete this issue.. it turns out that it was caused by some form of caching by my system..