Fix TypeError when parsing nested JSON objects in JWT payload #137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes issue where dissectPayl() function failed when encountering nested dict structures (e.g., resource_access['account'] = {'roles': [...]}).
The original code attempted to call castInput() on dict objects, which caused json.loads() to fail with TypeError: the JSON object must be str, bytes or bytearray, not OrderedDict.
Solution: Added type checking to handle nested dicts and lists before attempting to parse them as strings. Now properly displays nested JSON structures with proper indentation.
Fixes parsing of tokens with complex nested structures like Keycloak tokens containing resource_access and realm_access objects.