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
For more information, see the CONTRIBUTING guide.
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.
I would expect the payload not to be a string and instead be an object containing the fields
Payload is a string that is JSON serialized
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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
The text was updated successfully, but these errors were encountered: