[shaohuzhang1]

fix: [Portal] If you sign out of the portal while logged in and using an application that requires authentication, the system will trigger three "Access Denied" error messages.

[shaohuzhang1]

No syntax-only problem, but there are several important issues in this change:

1. force: true is not a Vue Router 4 option

router.replace({ ..., force: true }) is not a valid Vue Router 4 location property. It may cause a TypeScript error or be ignored at runtime. It will not force guards to re-run or force a same-route navigation.

If you need to force re-evaluation, prefer navigating to a public/entry route and letting the guard redirect, or explicitly revalidate auth. Avoid router.go(0) unless a full reload is acceptable.

2. Reusing route.params.accessToken after logout is risky

After auth.logout(), route.params.accessToken is presumably the old user's token. Passing it into the new chat-home location can:

• keep an invalid/stale token in the URL and browser history
• leak the previous token
• cause the guard to treat the old token as valid
• break if accessToken is undefined or string[], especially for a required named-route param
• produce the same location as the current route, causing a duplicated navigation and preventing guards from running

Prefer navigating to a token-less/public entry route and let the auth guard resolve the new anonymous session. If chat-home truly requires a token, obtain a fresh token from auth state after logout, not from the old route.

3. route is read asynchronously

route.meta.portal and route.params.accessToken are read inside .then() after auth.logout() completes. If logout triggers any navigation or route state change, you may read a different route than the one logout was initiated from. Capture the values before logout if that matters:

const wasPortal = Boolean(route.meta.portal)

4. Hard-coded route names may miss required params/query

portal-application-list and chat-home may require params such as tenant ID, locale, redirect, etc. If those are missing, navigation can fail or be redirected unexpectedly. Consider a single canonical post-logout entry route and let the guard decide the final destination.

5. .catch(() => {}) hides all failures

This swallows both logout failures and navigation failures. If logout fails, the user may still be authenticated but the UI may appear logged out. At minimum log the error; ideally show feedback and distinguish logout failure from navigation failure.

6. No loading/disabled state

Double-clicking logout can trigger multiple auth.logout() calls and multiple navigations. Consider a loading flag or disabling the logout action while it is in progress.

Suggested direction

const handleLogout = async () => {
  const wasPortal = Boolean(route.meta.portal)

  try {
    await auth.logout()

    await router.replace(
      wasPortal
        ? { name: 'portal-application-list' }
        : { path: '/' }, // or a known public entry route; let the guard resolve auth
    )
  } catch (error) {
    // log/show feedback instead of silently swallowing
    console.error('Logout or post-logout navigation failed', error)
  }
}

If chat-home requires accessToken, do not pass the old token. Either let the guard redirect from a public route, or use a freshly obtained token after logout. Also remove force: true.