jwt should have the "clockTolerance" option setting to avoid unexpected JWT "nbf" issue #11628
Unanswered
ceekoTanFuqi
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I met with the issue
unexpected JWT "nbf" (not before) claim value, timestamp is > now() at ib (/app/.next/server/app/api/auth/[...nextauth]/route.js:377:22546)The reason might be that the "nbf" in jwt is a little larger than now - maybe the "now" is not so accurate on different computers.
Any suggestions? Thanks.
Beta Was this translation helpful? Give feedback.
All reactions