How to generate the same signature as the JWT.IO website does?
@Believe2014 It seems that the jwt.io website does not have some options for specifying the base64 encoding with which way of URLEncoding to generate the same signature as your unit test.
However, according to the section 4 & 5 of RFC 4648, the differences between both signatures are using different characters for byte 62 & 63 and whether omits padding characters =.
So for converting the signature generated by jwt.io into yours, just using / instead of _, using + instead of -, and adding the padding characters = at the end of signature.