-
Notifications
You must be signed in to change notification settings - Fork 224
IAT is an int but it says it's not #9
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
Comments
@TheFlow95 Would you be able to share with me an example JWT that exhibits this problem. |
My JWT:
I found a trick to make it work:
But the algorithm (RS256) is not supported by your project. Can you add it please ? |
@TheFlow95 Your JWT is improperly encoded. Take a look at the payload: {
"exp": 1433168478,
"username": "florentin",
"iat": "1433082078"
} Note, IAT is a string instead of an integer as per the JWT specification where it states the value must be a number (not a string).
Your |
There's issue #6 tracking RS256 support. I'd welcome any pull request implementing this. |
Hello,
When I decode my JWT I got this error:
But the problem is that the iat is actually an integer. If I do a println of payload[key] in the validateDate function, it returns:
Optional(1433003301)
What is the problem ?
The text was updated successfully, but these errors were encountered: