---
title: "Dashboard Logout"
method: GET
path: "/dashboard/logout"
tags: ["dashboard"]
---

# Dashboard Logout

`GET /dashboard/logout`

## Request

- Base URL: `https://mcp.sentinelx.app` (the document declares no server; this is the origin it was published from)
- URL: `https://mcp.sentinelx.app/dashboard/logout`
- Auth: none declared

Log the user out completely.

Two-step process:
  1. Drop the local session cookie (so the hub forgets the user).
  2. Redirect to Keycloak's RP-initiated logout endpoint so it
     tears down the SSO session as well. Otherwise the next "Sign
     in" click would silently re-authenticate using the surviving
     Keycloak cookie, never showing the Google/GitHub picker.

When we have a cached id_token (set during login), we pass it as
`id_token_hint` and Keycloak performs the logout silently. Without
it (Redis miss, expired TTL, or pre-existing sessions from before
this feature), Keycloak shows its built-in "Are you sure?" page —
that's the safe fallback, not an error.

## Cookies

- `sentinelx_dash_session` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/sentinelx/apis/sentinelx-hub.md) · [All operations](https://skmtc.dev/sentinelx/apis/sentinelx-hub/llms.txt) · [OpenAPI document](https://skmtc.dev/sentinelx/apis/sentinelx-hub/revisions/d1f84924795e?raw)
