Skip to content

Two admin-authority models in eden-wire (admin principal vs admins-group membership) #321

Description

@ealt

eden-wire enforces admin authority two different ways:

  • require_admin (auth.py) checks the literal admin principal — used by the groups, workers, and checkpoints routers.
  • enforce_in_any_group(deps, request, ("admins",)) (_dependencies.py) checks transitive membership in the admins group — used by the tasks router (reassign).

These are semantically different authority models applied to different endpoints. A ground-up design picks one abstraction (group membership, since admin ≈ member-of-admins) and routes all gating through it.

See docs/design/2026-07-04-ground-up-review.md §2.7 / §4 (defect 3).

Metadata

Metadata

Assignees

No one assigned

    Labels

    cluster:identityOperator / worker identity, auth, multi-experimentenhancementNew feature or requestpriority:3-futureAspirational / deep-future / blocked on prerequisitestriage:readyIssue triage disposition

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions