K-W2 · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
With stateless sessions a stolen cookie must stop working after sign-out. Call the server's revocation endpoint on sign-out, and keep access tokens short-lived, re-minted from the refresh token.
Done when
After sign-out, a copy of the old cookie gets 401
Test
Depends on: K-S4, K-W1
**K-W2** · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
With stateless sessions a stolen cookie must stop working after sign-out. Call the server's revocation endpoint on sign-out, and keep access tokens short-lived, re-minted from the refresh token.
**Done when**
- After sign-out, a copy of the old cookie gets 401
- Test
**Depends on:** K-S4, K-W1
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 05:14:40 +00:00
Reopened: work started. Implemented on the PR #109 branch (second commit), since it's what makes cookie sessions safe to sign out of. Sign-out and sign-out-all revoke the refresh and access token through the server's revocation_endpoint (inbuxa-server#438). Test server/src/signout-revoke.test.ts in cookie mode: after sign-out a copy of the old cookie gets 401; against a server without revocation, sign-out still works and the copy keeps working (logged).
Reopened: work started. Implemented on the PR #109 branch (second commit), since it's what makes cookie sessions safe to sign out of. Sign-out and sign-out-all revoke the refresh and access token through the server's `revocation_endpoint` (inbuxa-server#438). Test `server/src/signout-revoke.test.ts` in cookie mode: after sign-out a copy of the old cookie gets 401; against a server without revocation, sign-out still works and the copy keeps working (logged).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
K-W2 · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
With stateless sessions a stolen cookie must stop working after sign-out. Call the server's revocation endpoint on sign-out, and keep access tokens short-lived, re-minted from the refresh token.
Done when
Depends on: K-S4, K-W1
Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.
Reopened: work started. Implemented on the PR #109 branch (second commit), since it's what makes cookie sessions safe to sign out of. Sign-out and sign-out-all revoke the refresh and access token through the server's
revocation_endpoint(inbuxa-server#438). Testserver/src/signout-revoke.test.tsin cookie mode: after sign-out a copy of the old cookie gets 401; against a server without revocation, sign-out still works and the copy keeps working (logged).Fixed in #109, merged to main; ships in the next 27.1 release candidate.