useMongocampSession
Answers "is my MongoCamp login still usable?" from the token alone. A token the server refuses is a readable 401 (server 1.6.1+), which the dependency and MongocampErrorAlert handle themselves; this composable covers what no request has noticed yet — a token whose own exp has passed. Used by the opt-in session guard.
const {
checkExpiry, // () => 'expired' | 'valid' | 'unknown' — token only, no request
currentState, // () => SessionState — token only, no request
verify, // () => Promise<'valid' | 'invalid' | 'unknown'> — asks the server (one request)
invalidateSession, // () => Promise<void> — awaits the dependency's logout()
} = useMongocampSession()type SessionState = 'active' | 'expired' | 'unknown'| State | Meaning |
|---|---|
active | The token's own exp says the session is fine |
expired | The token itself says it has run out |
unknown | Nothing can be said: unreadable or missing token, or server proxy mode |
unknown is never a reason to log anyone out.
checkExpiry and currentState
Read the exp claim of the stored token (decoded, not verified) with a 30 s leeway for clock skew. A token it cannot read — not a JWT, no numeric exp — and a missing token are unknown, not expired. currentState() is the same answer as a SessionState (valid → active). Neither sends a request, and the token value is never logged.
verify
Asks the server whether the stored token is still accepted (GET /auth/authenticated, 15 s timeout). valid = answered true; invalid = a readable 401 (or an explicit false); unknown = no token, server proxy mode, network failure, timeout or any other status. Only invalid is a reason to clear a session. This sees what checkExpiry cannot: a token the server stopped accepting — e.g. after a logout elsewhere (both logout routes invalidate the token server-side) — while its exp is still in the future. Used by the session guard's opt-in sessionGuardVerify.
invalidateSession
Clears the stored session through the dependency's own logout() (which blanks the token and profile in the mongocamp-session cookie) and awaits it. A no-op in server proxy mode.
Server proxy mode
There is no login, token or session in server proxy mode: every method reports unknown and logs nobody out.