You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing custom logic to generate my own JWT, I notice that the jti returned from encode function and the jti read in the decode function are completely different.
I'm afraid there's some other middleware (or perhaps core logic) that completely modifies the jti.
Additional context
While jti changes, I tried setting a new jti2 value on the JWT, which does get preserved after decode.
Logs
Encode - Original Token JTI: b7601006-9a3d-48f6-a172-b68b2b503555
Encode - Token JTI After Generation: b7601006-9a3d-48f6-a172-b68b2b503555
Decode - Decoded Token JTI: 6aeac235-0ce7-4243-af3f-9b99578769fb
The text was updated successfully, but these errors were encountered:
Environment
Reproduction
Describe the bug
When writing custom logic to generate my own
JWT
, I notice that thejti
returned fromencode
function and thejti
read in thedecode
function are completely different.I'm afraid there's some other middleware (or perhaps core logic) that completely modifies the
jti
.Additional context
While
jti
changes, I tried setting a newjti2
value on the JWT, which does get preserved after decode.Logs
The text was updated successfully, but these errors were encountered: