Is there an API to check if a user's jwt token expired? Need to show a message on the UI

[kotAPI]

Question 💬

I have added a jwt strategy and I've been trying to simulate token expiry on my local.

This is my lib/session

import { getServerSession } from "next-auth/next"

import { authOptions } from "@/lib/auth"

export async function getSession() {
  return await getServerSession(authOptions)
}

export async function getCurrentUser() {
  const session = await getSession()
  return session?.user
}

This is my jwt config at the moment

  jwt: {
    //maxAge: 60 * 60 * 24 * 30,
    // maxAge: 60 * 60 * 24 * DAYS, // 1 day
    maxAge: 60 * 60
  },

I am seeing this in my console.

https://next-auth.js.org/errors#jwt_session_error "exp" claim timestamp check failed {
  message: '"exp" claim timestamp check failed',
  stack: 'JWTExpired: "exp" claim timestamp check failed\n' +
    '    at __WEBPACK_DEFAULT_EXPORT__ (webpack-internal:///(sc_server)/./node_modules/jose/dist/node/esm/lib/jwt_claims_set.js:85:19)\n' +
    '    at jwtDecrypt (webpack-internal:///(sc_server)/./node_modules/jose/dist/node/esm/jwt/decrypt.js:13:87)\n' +
    '    at async Object.decode (webpack-internal:///(sc_server)/./node_modules/next-auth/jwt/index.js:44:26)\n' +
    '    at async Object.session (webpack-internal:///(sc_server)/./node_modules/next-auth/core/routes/session.js:25:34)\n' +
    '    at async AuthHandler (webpack-internal:///(sc_server)/./node_modules/next-auth/core/index.js:157:37)\n' +
    '    at async getServerSession (webpack-internal:///(sc_server)/./node_modules/next-auth/next/index.js:86:21)\n' +
    '    at async getSession (webpack-internal:///(sc_server)/./src/lib/session.js:11:12)\n' +
    '    at async getCurrentUser (webpack-internal:///(sc_server)/./src/lib/session.js:14:21)\n' +
    '    at async RootLayout (webpack-internal:///(sc_server)/./src/app/layout.js:19:18)',
  name: 'JWTExpired'
}

Is there an API i can use to find out if the said user's token expired? I'd like to show a message on the UI for the user to explain that their session has expired and they need to log back in

How to reproduce ☕️

Set a low maxAge on jwt config like this in your providers

  jwt: {
    maxAge: 60 * 60
  },

Contributing 🙌🏽

Yes, I am willing to help answer this question in a PR

[TuanManhCao]

I'm facing with the same issue, would love to hear from other. Thanks

[Aux9]

Here too

[ghritak]

If anyone facing this issue in 25, try putting maxAge in session as well, It solved my issue

session: {
    strategy: "jwt",
    maxAge: 72 * 60 * 60
  },
  jwt:{
    maxAge: 72 * 60 * 60
  }

[VitaliyPotapov]

Hmm, per the docs, jwt.maxAge defaults to session.maxAge: