Add a member by provider subject or email so OIDC sign-in works #320

Closed
opened 2026-10-27 13:35:50 +00:00 by sam · 1 comment
Owner

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 check once at the end; if it fails twice on the same problem, comment on this bead and stop.

Stop when

  • POST /api/orgs/{id}/members accepts {subject or email, role}, creates or binds a person identity and its membership.
  • The Org members tab (archie-core-kgxw.3) has the field.
  • A bound subject signs in and is authorized by its role (curl with a provider token, or a unit test of the principal).
    Then commit (Conventional Commits, scoped by package), bd close this 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-10

## 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 check` once at the end; if it fails twice on the same problem, comment on this bead and stop. ## Stop when - [ ] POST /api/orgs/{id}/members accepts {subject or email, role}, creates or binds a person identity and its membership. - [ ] The Org members tab (archie-core-kgxw.3) has the field. - [ ] A bound subject signs in and is authorized by its role (curl with a provider token, or a unit test of the principal). Then commit (Conventional Commits, scoped by package), `bd close` this 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-10_
sam added the highfeature labels 2026-10-27 13:35:50 +00:00
sam self-assigned this 2026-10-27 13:35:50 +00:00
sam closed this issue 2026-10-27 13:35:50 +00:00
Author
Owner

sam 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).

_sam 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).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#320