Part of inbuxa for Kubernetes, after 27.1 (tracking: inbuxa-charts#14).
Server OAuth tokens are sealed, not stored, so nothing can list an account's sessions or revoke one selectively; revocation is per credential (password change signs out everywhere). On Kubernetes the webmail runs with stateless cookie sessions and hides its sessions list for that reason (webmail #103).
Add a grant record per refresh-token chain (grant id carried in the tokens), so the server can list an account's grants (client, created, last used, IP/UA where known) and revoke one or all. Then:
The webmail's sessions list and 'sign out other sessions' work again in cookie mode.
The console gets a sessions view per account.
K-S4's denylist can become a revoked-grant check.
Done when
JMAP object to list and destroy grants, with permissions for self and admins
Validation rejects tokens of a revoked grant on every node
Webmail cookie mode shows the sessions list again
Part of inbuxa for Kubernetes, after 27.1 (tracking: inbuxa-charts#14).
Server OAuth tokens are sealed, not stored, so nothing can list an account's sessions or revoke one selectively; revocation is per credential (password change signs out everywhere). On Kubernetes the webmail runs with stateless cookie sessions and hides its sessions list for that reason (webmail #103).
Add a grant record per refresh-token chain (grant id carried in the tokens), so the server can list an account's grants (client, created, last used, IP/UA where known) and revoke one or all. Then:
- The webmail's sessions list and 'sign out other sessions' work again in cookie mode.
- The console gets a sessions view per account.
- K-S4's denylist can become a revoked-grant check.
**Done when**
- JMAP object to list and destroy grants, with permissions for self and admins
- Validation rejects tokens of a revoked grant on every node
- Webmail cookie mode shows the sessions list again
jcoffey-dev
added this to the 27.7 milestone 2026-11-18 06:37:11 +00:00
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.
Part of inbuxa for Kubernetes, after 27.1 (tracking: inbuxa-charts#14).
Server OAuth tokens are sealed, not stored, so nothing can list an account's sessions or revoke one selectively; revocation is per credential (password change signs out everywhere). On Kubernetes the webmail runs with stateless cookie sessions and hides its sessions list for that reason (webmail #103).
Add a grant record per refresh-token chain (grant id carried in the tokens), so the server can list an account's grants (client, created, last used, IP/UA where known) and revoke one or all. Then:
Done when