1.0: API token authentication (bearer token support) #87

Geschlossen
2026-02-19 22:39:46 +01:00 von clawbot geöffnet · 1 Kommentar
Mitarbeiter

The JSON API (/api/v1/*) currently only supports cookie-based session auth. For programmatic/CI use, it needs bearer token authentication.

Current state: APISessionAuth middleware only checks session cookies.

Needed for 1.0:

  • Generate API tokens (per-user, stored hashed in DB)
  • Accept Authorization: Bearer <token> header in API middleware
  • Token management UI (create, revoke, list)
  • Tokens should have optional expiry

This is essential for any CI/CD integration or scripted deployments via the API.

The JSON API (`/api/v1/*`) currently only supports cookie-based session auth. For programmatic/CI use, it needs bearer token authentication. **Current state:** `APISessionAuth` middleware only checks session cookies. **Needed for 1.0:** - Generate API tokens (per-user, stored hashed in DB) - Accept `Authorization: Bearer <token>` header in API middleware - Token management UI (create, revoke, list) - Tokens should have optional expiry This is essential for any CI/CD integration or scripted deployments via the API.
sneak hat diesen Issue 2026-02-19 22:43:34 +01:00 zum 1.5 Meilenstein hinzugefügt
clawbot hat sich das Issue 2026-02-20 09:28:41 +01:00 selbst zugewiesen
clawbot hat das Label merge-ready 2026-02-20 09:28:42 +01:00 hinzugefügt
Besitzer

WONTFIX

WONTFIX
sneak hat diesen Issue 2026-02-20 11:43:11 +01:00 geschlossen
Anmelden, um an der Diskussion teilzunehmen.
2 Beteiligte
Nachrichten
Fällig am
Kein Fälligkeitsdatum gesetzt.
Abhängigkeiten

Keine Abhängigkeiten gesetzt.

Referenz: sneak/upaas#87