Bug: Admin-bootstrap race (first-user admin assignment) #79

New issue

Closed

opened 2026-07-08 02:40:30 +00:00 by icub3d · 0 comments

icub3d commented

2026-07-08 02:40:30 +00:00

Owner

Severity: High (correctness) — found in code review 2026-07-07.

Problem

server/src/auth/handlers.rs:98: the first user becomes admin via list_users().len() == 1. Two concurrent registrations can interleave (A creates, B creates, then both list → 2) so that no one receives the admin role, leaving the server without an administrator.

Fix

Perform the bootstrap (first-user → admin) atomically — a transaction with a guard, or a dedicated one-time bootstrap step / config-driven owner pubkey.

Acceptance

Concurrent first-registrations deterministically produce exactly one admin (test)

**Severity: High (correctness)** — found in code review 2026-07-07. ## Problem `server/src/auth/handlers.rs:98`: the first user becomes admin via `list_users().len() == 1`. Two concurrent registrations can interleave (A creates, B creates, then both list → 2) so that **no one** receives the admin role, leaving the server without an administrator. ## Fix - [ ] Perform the bootstrap (first-user → admin) atomically — a transaction with a guard, or a dedicated one-time bootstrap step / config-driven owner pubkey. ## Acceptance - [ ] Concurrent first-registrations deterministically produce exactly one admin (test)

icub3d added the

area:api

status:planned

type:bug

labels

2026-07-08 02:40:30 +00:00

icub3d referenced this issue from a commit

2026-07-08 03:39:28 +00:00

fix(auth): make founding-admin bootstrap atomic

icub3d referenced this issue from a pull request that will close it,

2026-07-08 03:39:50 +00:00

fix(auth): make founding-admin bootstrap atomic #96