Phase 5: API Tokens + Robot Users (CI/CD Upload) #4

Closed
opened 2026-02-02 19:58:45 +01:00 by qwc · 0 comments
Owner

Token generation (crypto/rand, sha256 hash), Bearer token auth middleware, POST /api/project/{slug}/upload endpoint, admin UI for robot users and tokens, scoped permissions via project_access.

Tests needed:

  • Unit: token generation, hashing, validation, Bearer header extraction
  • Integration: create robot → generate token → curl-style upload → docs served
  • Integration: revoked/expired token returns 401, missing access returns 403
Token generation (crypto/rand, sha256 hash), Bearer token auth middleware, `POST /api/project/{slug}/upload` endpoint, admin UI for robot users and tokens, scoped permissions via project_access. **Tests needed:** - Unit: token generation, hashing, validation, Bearer header extraction - Integration: create robot → generate token → curl-style upload → docs served - Integration: revoked/expired token returns 401, missing access returns 403
qwc closed this issue 2026-02-02 20:09:18 +01:00
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.

Dependencies

No dependencies set

Reference
qwc-open/asiakirjat#4
No description provided.