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 Type inconsistency #52

Open
ga1az opened this issue Sep 12, 2024 · 0 comments · May be fixed by #53
Open

iat Type inconsistency #52

ga1az opened this issue Sep 12, 2024 · 0 comments · May be fixed by #53
Labels
bug Something isn't working

Comments

@ga1az
Copy link

ga1az commented Sep 12, 2024

What version of Elysia is running?

1.1.12

What platform is your computer?

Darwin 23.6.0 arm64 arm

What steps can reproduce the bug?

Sign any payload with the JOSE librery

return new SignJWT(payload1)
		.setProtectedHeader({ alg: 'HS256' })
		.setIssuedAt()
		.setExpirationTime('7d')
		.sign(key)

and verify with the elysia-jwt

{ jwtAccess, body: { name } }) => {
			return jwtAccess.verify(jwt)
		}

This generates an error due to the iat check in the iat code: t.Optional(t.String())

What is the expected behavior?

No error on schema verification

What do you see instead?

No response

Additional information

No response

Have you try removing the node_modules and bun.lockb and try again yet?

No response

@ga1az ga1az added the bug Something isn't working label Sep 12, 2024
@ga1az ga1az linked a pull request Sep 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant