Solution skill
User still logged in after logout: app session vs Auth0 session vs federated
Complete solution
Symptom: after logout, visiting login instantly re-authenticates. Cause: only one of the two sessions was cleared. Confirmation: check whether the Auth0 session cookie survives and whether /v2/logout was hit. Not the full reference manual.
TL;DR: Symptom: after logout, visiting login instantly re-authenticates. Cause: only one of the two sessions was cleared. App cleared its own session but never hit YOUR_HOST/v2/logout. Confirm - DevTools network: after logout, is there a request to /v2/logout?
The fix
- App cleared its own session but never hit
YOUR_HOST/v2/logout. The Auth0 SSO cookie survives; the next authorize silently re-authenticates. - Hit /v2/logout but returnTo was not allowlisted, so Auth0 showed an error page and the user closed it mid-flow; the session may or may not have cleared.
- Federated IdP session: the user logged in via Google/enterprise; Auth0 session cleared but the IdP session survives, so the next login round-trips the IdP silently. Needs
federated=trueon logout. - SDK logout called without logoutParams, so no redirect happened at all (SPA cleared local state only).
- DevTools network: after logout, is there a request to /v2/logout? If not, the app never logged out of Auth0.
- After logout, open the tenant domain in a tab: if the Auth0 session cookie is still present, /v2/logout did not complete.
- Tenant logs: logout events (type
slo/flo) confirm server-side logout.
When to use this
- This covers exactly what the title says: User still logged in after logout.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.
When not to use this
- You are doing a different workflow with User; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.
Compatibility
- Not pinned to a specific version; follows current User behavior.
Evidence
Auth0's logout docs describe the /v2/logout endpoint, the returnTo allowlist requirement, and the federated logout option. Logout event types are in the log event codes. Verified against live docs 2026-09-26.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_FFYBCKUwY3m84XFnctXgAw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">User still logged in after logout: app session vs Auth0 session vs federated <span>— Vectle</span></a>