diff options
| author | tv <tv@krebsco.de> | 2026-11-09 12:25:09 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-09 13:32:05 +0100 |
| commit | d12ccc782d8e6eab46eb6e0976b747dca1013b36 (patch) | |
| tree | de9d5ae9135a182dbb19a6067d240054483561d4 /src/api/dashboard | |
| parent | b0e711f9f7e0d2d9f6b39dd987004d2f9b1dcda7 (diff) | |
access: ending a single session
Logging out of the dashboard (`DELETE /auth/session`) only cleared the cookie: the
session's tokens stayed taken until they expired, by every node. Ending them took
`POST /auth/logout`, which ends all of a user's sessions.
Now `DELETE /auth/session` ends the session of the token it comes with (the cookie, or
a bearer token): where the swarm has a registry, it is recorded as
`_continuum/sessions/<user>/<session>` (`registry::session_path`), its value until when
the session would have lasted, and every node refuses the session's tokens once the
change reaches it (`token::Refused::Ended`): the page's own, its narrow tokens, and one
handed to another member's dashboard, all refreshed from it and keeping its ID. The
rules take the entry from the user itself or one who manages users, as a logout. A
remake's snapshot leaves out entries past that time, a user's map where none is left:
their tokens are expired anyway.
Without a registry the document can't record it: the node ending it refuses the
session's tokens itself (`AppState::ended_sessions`, until it restarts), others take
them until they expire, as a logout there is refused.
Diffstat (limited to 'src/api/dashboard')
0 files changed, 0 insertions, 0 deletions
