Any suggestion what could cause of getting this error message?
It seems it's related to refresh token, but I'm not getting why jwtDecode is trying to decode refresh_token.

Invalid token specified: missing part #2

I see that only for JWT tokens this package will look at exp value otherwise we need to set it ourselves. Is it possible somehow to set/change programaticali after login? I get expiresAt data from some API and would like to set the maxAge of refreshToken to expiresAt - 30 seconds, so I can call refresh before it actually expires. I need to make user's token not to expire in case someone is entering data/text on a page too long.

Trying to extend the type definition for User according to the docs does nothing: https://nuxt-3-auth.github.io/guide/typescript.html

the type is still any

We are encountering an issue when making API calls after successfully refreshing the token. Upon completing the token refresh process, we proceeded to call the previous API again but encountered an unexpected error. The system redirected users back to the login page.

This issue is causing a disruption to the user experience and requires intervention to resolve.

Can you please clarify why I can't get loggedIn.value on SSR is this intended behaviour?

here is how my code looks like:

  const { $auth } = useNuxtApp()
  const { user, loggedIn } = $auth

  if (import.meta.server) {
    console.log(`🆘 ~ SERVER loggedIn:`, loggedIn)
    console.log(`🆘 ~ SERVER loggedIn:`, loggedIn.value)
  }

  if (import.meta.client) {
    console.log(`🆘 ~ CLIENT loggedIn:`, loggedIn)
    console.log(`🆘 ~ CLIENT loggedIn:`, loggedIn.value)
  }

And here is the result:
SSR:

CLIENT:

Describe the feature

There is a limitation so far, it requires to use jwt tokens (also mentioned on the docs). If your token is not a jwt one will cause this error.

Proposal

Add 2 more options token.maxAge and refreshToken.maxAge to specific the cookie maxAge for access token and refresh token if tokens are not JWT.

Related issue

#16

Is production ready or still beta or something?
Sorry for this dump question.

Is it possible to somehow completely remove the /login from package? I have the same route and would like to use my own form that is styled like the rest of website.