Skip to content
New issue

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

Token Payload is JSON serialized #448

Open
5 of 7 tasks
Synforge opened this issue Oct 1, 2023 · 0 comments
Open
5 of 7 tasks

Token Payload is JSON serialized #448

Synforge opened this issue Oct 1, 2023 · 0 comments

Comments

@Synforge
Copy link

Synforge commented Oct 1, 2023

Prerequisites

  • Is it a bug?
  • Is it a new feature?
  • Is it a question?
  • Can you reproduce the problem?
  • Are you running the latest version?
  • Did you check for similar issues?
  • Did you perform a cursory search?

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

  1. Create a JWT through ObtainJSONWebToken
  2. Decode the JWT and notice that the payload is a string that is JSON serialized, this is fairly non-standard, I haven't seen this in any other JWT

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant