Problem refresh page

[memellow85]

Environment

---

• Operating System: Darwin
• Node Version: v20.17.0
• Nuxt Version: 3.15.1
• CLI Version: 3.20.0
• Nitro Version: 2.10.4
• Package Manager: [email protected]
• Builder: -
• User Config: alias, app, srcDir, debug, dev, devServer, ssr, devtools, modules, auth, vite, compatibilityDate
• Runtime Modules: @sidebase/[email protected]
• Build Modules: -

---

Reproduction

I have this endpoints:

http://example.com/user/token -> response -> { access_token: "", refresh_token: "" }
http://example.com/user/token-refresh -> body -> { refresh_token: "" }  -> response -> { access_token: "", refresh_token: "" }
http://example.com/user/my-user -> response -> { id: "", name: "" }

My configuration is this:

auth: {
    isEnabled: true,
    disableInternalRouting: true,
    disableServerSideAuth: true,
    baseURL: 'http://example.com',
    provider: {
      type: 'local',
      pages: {
        login: '/login',
      },
      endpoints: {
        signIn: { path: '/user/token', method: 'post' },
        signOut: false,
        signUp: false,
        getSession: { path: '/user/my-user', method: 'get' },
      },
      token: {
        signInResponseTokenPointer: '/access_token',
      },
      refresh: {
        isEnabled: true,
        endpoint: { path: '/user/token-refresh', method: 'post' },
        refreshOnlyToken: false,
        token: {
          signInResponseRefreshTokenPointer: '/refresh_token',
          refreshResponseTokenPointer: '/access_token',
          refreshRequestTokenPointer: '/refresh_token',
        },
      },
      session: {
        dataType: {
          id: 'string',
          name: 'string',
        },
        dataResponsePointer: '/',
      },
    },
    sessionRefresh: {
      enablePeriodically: false,
      enableOnWindowFocus: true,
    },
    globalAppMiddleware: {
      isEnabled: true,
      addDefaultCallbackUrl: false,
    },
  },

My files .vue:
index.vue

<script setup lang="ts">
const { signOut, status, data } = useAuth()

const test = () => {
  signOut({ callbackUrl: '/login' })
}
</script>

<template>
  <div>
    {{ status }}<br />
    {{ data }}<br />
    <button @click="test">logout</button>
  </div>
</template>

login.vue

<script setup lang="ts">
const { signIn, status, data } = useAuth()

const username = ref('user')
const password = ref('password')

definePageMeta({
  auth: {
    unauthenticatedOnly: true,
    navigateAuthenticatedTo: '/'
  }
})

const submit = (): void => {
  signIn({ name: username.value, password: password.value }, { callbackUrl: '/' })
}
</script>

<template>
  <div>
    {{ status }}<br />
    {{ data }}<br />
    <input v-model="username" type="text" />
    <input v-model="password" type="password" />
    <button @click="submit()">sign in</button>
  </div>
</template>

Describe the bug

Hi, I have a problem when refresh page after login... After login I go to index.vue page but if I refresh page... I go always in login.vue... why?

Thanks a lot

Additional context

No response

Logs

No response

[daniel-ness]

Had a similar issue on a new project. The solution for me was to disable SSR mode in Nuxt

[memellow85]

I have already set ssr to false.
Probably the problem is because when the page is refreshed the status is loading... the status is changed after the getSession I think

[LeonidevFR]

I second this issue, I experience the same bug.

My App doesn't redirect to the router next route when coming from an external link (an tag on a second app, in my case).
I noticed as well that it goes through the authentication before accessing the app, and it loses the requested routes in the process.

I tried and disabled the ssr in my config and it works fine. But this solution won't be durable, for many obvious reasons...

[MuhamadAdrian]

in my case, if i'm truned of the ssr. i can't login because the api return text/html not application/json. But i think that is from my backend.

The issue previously i saw was this :

And this happened on server side, when refreshing the page. If i'm turned off the refresh schema. auth.token not removed, but i think because this error happened on server side, it's make the auth.token cookies removed and logged out