Manage Temper Operators and sessions #22

Open
opened 2026-07-14 22:32:26 -04:00 by caleb-brown · 0 comments
Owner

What to build

Existing Temper Operators can safely manage additional equal-privilege Operators and active sessions without public signup or an enterprise RBAC system.

Acceptance criteria

  • An authenticated Operator can create another Operator through a secure invitation or bootstrap-reset flow.
  • Operators can rotate their passwords and administrators can disable an account without exposing password material.
  • Temper prevents removal or lockout of the last usable Operator.
  • Sessions are server-side, expiring, revocable, securely cookie-bound, and invalidated when required by account changes.
  • Login throttling and CSRF protection cover all authentication and mutating Operator actions.
  • Operator and session lifecycle changes are append-only audited.
  • Security tests cover fixation, expiry, revocation, throttling, CSRF, disabled accounts, and last-Operator protection.

Blocked by

  • #9 — Boot a secure Temper Deployment
## What to build Existing Temper Operators can safely manage additional equal-privilege Operators and active sessions without public signup or an enterprise RBAC system. ## Acceptance criteria - [ ] An authenticated Operator can create another Operator through a secure invitation or bootstrap-reset flow. - [ ] Operators can rotate their passwords and administrators can disable an account without exposing password material. - [ ] Temper prevents removal or lockout of the last usable Operator. - [ ] Sessions are server-side, expiring, revocable, securely cookie-bound, and invalidated when required by account changes. - [ ] Login throttling and CSRF protection cover all authentication and mutating Operator actions. - [ ] Operator and session lifecycle changes are append-only audited. - [ ] Security tests cover fixation, expiry, revocation, throttling, CSRF, disabled accounts, and last-Operator protection. ## Blocked by - [#9](https://git.caleb-brown.dev/caleb-brown/temper/issues/9) — Boot a secure Temper Deployment
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
caleb-brown/temper#22
No description provided.