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

fix: seconds to ms #104

Merged
merged 1 commit into from
Apr 24, 2024

Conversation

TimoGlastra
Copy link
Collaborator

another fix related to milliseconds vs seconds

Signed-off-by: Timo Glastra <[email protected]>
@TimoGlastra
Copy link
Collaborator Author

@nklomp could you take a look at this PR?

@nklomp
Copy link
Contributor

nklomp commented Apr 10, 2024

Yeah, need to have a closer look into it. Because I wasn't entirely sure about it if I remember correctly.

@nklomp
Copy link
Contributor

nklomp commented Apr 10, 2024

To be clear it revolved more around also renaming the first part or not. I only quickly looked at it a few days ago from mobile phone

@nklomp nklomp merged commit a453002 into Sphereon-Opensource:develop Apr 24, 2024
1 check passed
@nklomp
Copy link
Contributor

nklomp commented Apr 24, 2024

Made a small change. The createdAt from the state manager is in milliseconds. The expiration arguments and JWT claims are in seconds. So the first change IMO was incorrect. Changed it to divide the createdAt by 1000 to convert it to seconds. Then add the tokenExpiresIn and compare that to iat

iat > (createdAt/1000 + tokenExpiresIn)

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

Successfully merging this pull request may close these issues.

2 participants