Revoke an API key with immediate effect #10

New issue

Open

opened 2026-07-01 01:01:02 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 01:01:02 +00:00

(Migrated from github.com)

Problem

Compromised or retired keys must stop working immediately. Operators need a revoke action that takes effect on the next request.

Acceptance criteria

Revoking a key marks it revoked with a timestamp and operator, and it is rejected on subsequent API calls
A revoked key cannot be un-revoked; a new key must be issued instead
The keys list visually distinguishes active, revoked, and rotated keys
Revocation is recorded in the audit log

## Problem Compromised or retired keys must stop working immediately. Operators need a revoke action that takes effect on the next request. ## Acceptance criteria - [ ] Revoking a key marks it revoked with a timestamp and operator, and it is rejected on subsequent API calls - [ ] A revoked key cannot be un-revoked; a new key must be issued instead - [ ] The keys list visually distinguishes active, revoked, and rotated keys - [ ] Revocation is recorded in the audit log

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

Directorium/Site#10

No description provided.

Rows
Columns