- migration 0002: users.verified boolean, default false
- verified rides in the JWT (role + verified claims)
- POST /users/{id}/verify + /unverify, admin-only (403 otherwise)
- Issue now takes the whole user so trust claims travel in the token
- unit + integration + admin-flow tests
10 lines
399 B
PL/PgSQL
10 lines
399 B
PL/PgSQL
BEGIN;
|
|
|
|
-- A "verified" account is a trusted contributor: the coordinator accepts its
|
|
-- workers' results directly, without quorum cross-checking. Distinct from role
|
|
-- (which governs what a user may do with their own jobs). Granted by an admin,
|
|
-- never self-served; defaults to false, so a fresh account is untrusted.
|
|
ALTER TABLE users ADD COLUMN verified boolean NOT NULL DEFAULT false;
|
|
|
|
COMMIT;
|