Dashboard operator is a person owning org-sys, not the system identity #317
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#317
Reference in new issue
Block a user
Goal
The dashboard operator acts as a person who owns org-sys, not as the
systemidentity, without requiring an OIDC provider.Context
internal/webui/authorize.go:58requestPrincipal: with no acting identity (shared token) it returnsaccess.SharedTokenOwner()(internal/domain/access/request.go), a synthetic system owner with no membership row.internal/infrastructure/staterpc/personal_tokens.go:24), audit rows name system (internal/webui/api_identities.go:88-93webAudithardcodesidentity.SystemID), and the org has no person owner, so enabling OIDC later orphans it.queries/orgupgrade.sql+internal/infrastructure/postgres/orgs.goUpgradeDefaultOrg.internal/domain/identity).Steps
operator(display name "Operator") and give it anownermembership in org-sys. (Use a new org_upgrades phase name; extend the CHECK constraint in a migration.)requestPrincipalresolves the org-sys owner person via the Principals source instead ofSharedTokenOwner()when one exists; fall back to SharedTokenOwner only if none. Keep machine callers (service tokens, run credentials) unchanged.webAudit: use the request's principal identity, falling back to system only when there is none.Out of scope
OIDC configuration UI, subject binding, instance admin, renaming the operator (the Identities page already renames).
Stop when
operator, owner of org-sys (run the upgrade twice: still one).task checkpasses.feat(access): the dashboard operator is a person owning org-sys, close. Stop.Rules for this ticket
bd create(one line of why) and carry on. Do not fix it.task checkonce at the end. If it fails twice on the same problem, stop and write what failed in a bead comment (bd comments add <id> "...") instead of looping.Close reason
Closed
Imported from beads
archie-core-kgxw.4· GitHub #1276 · type feature · priority P1 · created 2026-10-05 · closed 2026-10-05