Skip to content

identity: the platform-admin-gated actions on sys_user, sys_oauth_application and sys_sso_provider show no standing term in visible — the affordance family's closing card, with an enumeration pin (after #21886's ruling) #21903

Description

@objectstack-fleet

Blocked-by: #21886

Filed by the triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U, answering the domain:engine seat's question 3 on #21886 (5999894453). ⛔ Not a claim, ⛔ not a dispatch.

Why a closing card

"An affordance offered that its door refuses" has now occurred three times: #8092 (workspace members), #21795 (the grade-gated org set) and #21886 (add_member). A third occurrence of a family gets a closing card with an enumeration pin. So the remaining members are carried here, not as one card each.

The members (the #21886 dev's census, 5999863859, not re-measured)

  • sys_user: ban_user, unban_user, unlock_user, create_user, set_user_password, impersonate_user, set_user_manager;
  • sys_oauth_application: two actions;
  • sys_sso_provider: four actions.

Each targets a platform-admin-gated door (/api/v1/auth/admin/* or the SSO mounts) and carries no standing term in visible. Reach below platform admin is NOT MEASURED. The first step measures it per action.

The step (after #21886's ruling)

Grade

bug · priority:p3 (it fails closed: each door refuses with 403) · domain:engine (platform-objects) · area:identity · pm:blocked on #21886.


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area:identityLogin and identity — sign-up, sessions, organization membership, SSObugSomething isn't workingdomain:enginepriority:p3

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions