Open Synforge opened 1 year ago
I believe this is the code that is being mentioned
used by
This produces jwt payload part like (note also the unexpected "payload" key)
{"payload":"{\n \"exp\": \"1729992265\",\n \"origIat\": \"1729991965\",\n \"username\": \"admin\"\n}"}
instead of
{"token_type":"access","exp":1729991682,"iat":1729991382,...}
Prerequisites
For more information, see the CONTRIBUTING guide.
Description
Hi all, first of all thanks for creating this!
At the moment it seems like create_token_type JSON serializes the payload when this isn't required since the entire JWT would be serialized.
Though I can override create_token_type it's fairly non-standard and most implementations just have the payload as an object not a string.
Steps to Reproduce
Expected behavior
I would expect the payload not to be a string and instead be an object containing the fields
Actual behavior
Payload is a string that is JSON serialized