Add a member by provider subject or email so OIDC sign-in works #320
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#320
Reference in new issue
Block a user
Goal
An owner can add a person by OIDC subject or email with a role, and that person can then sign in and act with it.
Evidence
internal/webui/auth.go:287-300 refuses a verified but unbound subject (ErrSubjectUnbound). BindIdentitySubject RPC exists (internal/infrastructure/staterpc/identities.go:83) but no HTTP route calls it. Depends on archie-core-kgxw.2 (membership API).
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
c619da95: POST /api/orgs/{id}/members adds by subject or email, Org members tab has the field, TestOrgMemberAdd signs the added person in by role
Imported from beads
archie-core-kgxw.7· GitHub #1274 · type feature · priority P1 · created 2026-10-05 · closed 2026-10-10sam wrote (originally 2026-10-10):
Landed as
3a9bb2b4(c619da95 was never merged). An email placeholder is single-use: the first verified sign-in moves it onto the provider subject (ClaimIdentitySubject).