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

iat being set to null is not handled properly #363

Open
Colin-b opened this issue Sep 25, 2024 · 0 comments
Open

iat being set to null is not handled properly #363

Colin-b opened this issue Sep 25, 2024 · 0 comments

Comments

@Colin-b
Copy link

Colin-b commented Sep 25, 2024

If iat is provided, but the value is null (or None once deserialized), a TypeError is raised instead of a JWTClaimsError.

I think the following piece of code should handle TypeError as well as ValueError:

except ValueError:

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