We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm using last release 2.2.7.
It seems to be a similar error as in #21 that was fixed in v1.3.5. However, it seems exactly the same issue as in #106
So there is maybe another json.loads that should be changed in json.dumps.
json.loads
json.dumps
While decoding a token:
Token payload values: … [+] prop_a = JSON object: [+] aaa = "['stuff_a', 'stuff_b', 'stuff_c', 'stuff_d']" [+] prop_b = JSON object: Traceback (most recent call last): File "/usr/share/jwt-tool/jwt_tool.py", line 2103, in <module> rejigToken(headDict, paylDict, sig) File "/usr/share/jwt-tool/jwt_tool.py", line 1299, in rejigToken comparestamps, expiredtoken = dissectPayl(paylDict) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/jwt-tool/jwt_tool.py", line 1203, in dissectPayl if type(castInput(paylDict[claim][subclaim])) == str: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/jwt-tool/jwt_tool.py", line 595, in castInput jsonInput = json.loads(newInput) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/json/__init__.py", line 339, in loads raise TypeError(f'the JSON object must be str, bytes or bytearray, ' TypeError: the JSON object must be str, bytes or bytearray, not OrderedDict
The data:
… "prop_a": { "aaa": [ "stuff_a", "stuff_b", "stuff_c", "stuff_d" ] }, "prop_b": { "bbb": { "ccc": [ "stuff_e", "stuff_f", "stuff_g" ] } }, …
The text was updated successfully, but these errors were encountered:
It seems #114 and #111 are trying to fix OrderedDict casting issues.
Sorry, something went wrong.
I'm facing the same issue, #111 fixed it in my case.
No branches or pull requests
I'm using last release 2.2.7.
It seems to be a similar error as in #21 that was fixed in v1.3.5. However, it seems exactly the same issue as in #106
So there is maybe another
json.loads
that should be changed injson.dumps
.While decoding a token:
The data:
The text was updated successfully, but these errors were encountered: