External JSON parsing error when object/array claim contains escape characters

[ufownl]

Hi, version 2.3.1 still has a small problem. If an object/array claim contains escape characters, it will lead external JSON parsing error. I checked the relevant code and found that the issue is here. The object/array claims should not be unescaped, they should retain their original content for the external JSON parser.

Additionally, I found that the function l8w8jwt_unescape_claim only escapes \" for keys, \" and \/ for values, and no other escape characters. I'm not sure if this is a feature or an issue.

[GlitchedPolygons]

@ufownl Hi :)

Unfortunately I don't have a lot of time to look into this atm, would it be ok for you to post more info (such as token used for decoding, expected behavior and actual behavior)?
I'm also open to review pull requests in case you feel like fixing it yourself 😃

[ufownl]

This issue has almost no impact on my project at present, and I can try to fix it when I have time in the future. :)

[ufownl]

This issue has been fixed in PR #44, so it can be closed.