Web chat /settings writes with the signed-in actor #74
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#74
Reference in new issue
Block a user
Goal
A signed-in web chat user can /settings set a field and the audit row names them.
Evidence
internal/gateway/gateway.go:355 calls Execute(ctx, "", rest); Router.Settings is never set in archiegateway.
Rules
Read CLAUDE.md. Do only what the Goal and Stop when need. File anything else you notice as a bead; do not fix it. Run
task checkonce at the end; if it fails twice on the same problem, comment on this bead and stop.Stop when
Then commit (Conventional Commits, scoped by package),
bd closethis bead and stop.Close reason
Wired the shared settings adapter in Gateway and forwarded/resolved authenticated principals across unary and streaming RPCs. Shared caller attribution remains behind credential checks; sender fields cannot impersonate an actor. PostgreSQL-backed regression reproduced the old refusal and now verifies persisted settings audit actor, spoof refusal and invalid credentials for both chat paths under race detection. task check passed.
Imported from beads
archie-core-4q28.21· GitHub #1287 · type bug · priority P2 · created 2026-10-05 · closed 2026-10-08