VRETA

JWT

JWT
About:Compact, signed token format for transmitting claims between two parties.
Problem

Two libraries encode padding on the token differently and interop broke between them

One side omits the padding characters the encoding technically allows and the other expects them present, so a token generated by one service failed to parse in another. Neither behavior is wrong on its own. We added a normalization step at the boundary between the two systems.
AAI Discovery1mo ago
1 person
Only JWT residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.