App passwords: expiry with per-deployment require-toggle, compact table + modal create, cache revocation fix #751

Closed
opened 2026-09-25 19:13:34 +00:00 by Cordy · 0 comments
Owner

OpenCloud-comparison round (#695): close the App-Tokens feature gap and adopt their compact layout (approved mockup: heading + New button + 4-column table).

Server

  • AppPassword gains ExpiresAt (zero = never). Create takes an expiry.
  • Authenticate refuses expired records — including on verified-cache hits: the cache entry now carries the record id and every hit re-checks liveness + expiry in the store. This also fixes a live bug: a revoked app password currently keeps authenticating from the cache until process restart.
  • Expired records are lazily purged (filtered from List/auth, cleaned on the next persist).
  • New runtime setting appPwRequireExpiry (default off) through the existing GET/PUT /api/v1/settings: when on, create without an expiry → 422. Research note: no standard mandates expiry (NIST 800-63B leaves authenticator lifetime as a risk decision; BSI ORP.4.A23 moved away from time-based changes) — hence a per-deployment toggle, not a hard requirement.

Web UI

  • Account settings → App passwords becomes heading + "New" + compact table: Name | Created | Expires | Actions (Delete). Em-dash for never-expiring (all pre-existing) entries; dates within 14 days shown ember with a relative note.
  • Create moves into a modal dialog: device name + expiry date (optional when toggle off, required + prefilled +3 months when on), then the one-time secret + Copy in the same dialog.
  • Admin → Instance group gets the "Require expiry on app passwords" toggle row (settings PUT round-trip, same pattern as peeringEnabled #134).
  • Name stays "App passwords"; i18n ×4 for all new copy.
OpenCloud-comparison round (#695): close the App-Tokens feature gap and adopt their compact layout (approved mockup: heading + New button + 4-column table). **Server** - `AppPassword` gains `ExpiresAt` (zero = never). `Create` takes an expiry. - `Authenticate` refuses expired records — including on verified-cache hits: the cache entry now carries the record id and every hit re-checks liveness + expiry in the store. This also fixes a live bug: a **revoked** app password currently keeps authenticating from the cache until process restart. - Expired records are lazily purged (filtered from List/auth, cleaned on the next persist). - New runtime setting `appPwRequireExpiry` (default off) through the existing GET/PUT /api/v1/settings: when on, create without an expiry → 422. Research note: no standard mandates expiry (NIST 800-63B leaves authenticator lifetime as a risk decision; BSI ORP.4.A23 moved away from time-based changes) — hence a per-deployment toggle, not a hard requirement. **Web UI** - Account settings → App passwords becomes heading + "New" + compact table: Name | Created | Expires | Actions (Delete). Em-dash for never-expiring (all pre-existing) entries; dates within 14 days shown ember with a relative note. - Create moves into a modal dialog: device name + expiry date (optional when toggle off, required + prefilled +3 months when on), then the one-time secret + Copy in the same dialog. - Admin → **Instance** group gets the "Require expiry on app passwords" toggle row (settings PUT round-trip, same pattern as peeringEnabled #134). - Name stays "App passwords"; i18n ×4 for all new copy.
Cordy closed this issue 2026-09-25 19:41:22 +00:00
Sign in to join this conversation.
No labels
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.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#751
No description provided.