Skip to content

Expose verified HOP-1 claims to tool policy - #16

Merged
lbelyaev merged 2 commits into
mainfrom
feat/hop1-claims-policy-input
Jul 29, 2026
Merged

lbelyaev merged 2 commits into
mainfrom
feat/hop1-claims-policy-input

Conversation

@lbelyaev

Copy link
Copy Markdown
Contributor

What changed

  • add the verified JWT claim set to ToolPolicyInput
  • pass claims through both the GitHub and Google Workspace wrappers
  • assert that OPA receives claims while argument redaction remains intact

Why

Downstream control planes can attenuate one human principal differently for separate runtime instances only when policy can inspect the authority claims carried by the already-verified HOP-1 token. Email alone collapses those instances into one authority set.

This remains issuer-agnostic: mcp-gw forwards the verified claims to its trusted policy evaluator without interpreting a downstream claim schema.

Validation

  • bun run ci
  • 193 tests pass
  • TypeScript typecheck, ESLint, and formatting checks pass

@lbelyaev
lbelyaev marked this pull request as ready for review July 27, 2026 20:36
lbelyaev added a commit to apelogic-ai/steward that referenced this pull request Jul 28, 2026
* S1: runtime-bound credential isolation

Exit criteria:
  - acting-user tool call succeeds (e2e_s1_tool_call_as_acting_user)
  - out-of-grant, forged-SVID, and cross-user reuse attempts fail closed

Guarantees re-run: G-2 green against OpenShell v0.0.90 + carried identity patch, SPIRE 1.15.2, and mcp-gw c2af10d9 + #1634acece3
Upstream dependencies recorded: NVIDIA/OpenShell#2012, #2184, #1970; apelogic-ai/mcp-gw#16

* fix: close S1 authority and provider lifecycle gaps

Revoke mint authority when deletion begins, provision and reconcile the gateway provider in every OpenShell workspace, and exercise a legitimate second runtime for cross-user isolation.

Add executable pinned G-2 conformance evidence and run it through the aggregate gate.

* fix: make S1 reconciliation and conformance exact

Reconcile the OpenShell gateway attachment symmetrically so removed tools detach it and unchanged state remains mutation-free. Replace source-shape evidence with one executed upstream-focused G-2 negative test in both pinned and latest lanes, while retaining the separate S1 E2E exit criterion.

* fix: make G-2 evidence exercise verified claims

Require policy to authorize from normalized HOP-1 identity and runtime tool claims before credential resolution. Count the nested Bun execution exactly and require its validated success sentinel alongside the Rust wrapper result. Latest upstream remains a recorded finding until apelogic-ai/mcp-gw#16 lands; pinned evidence carries that patch.

* fix: make G-2 test cross-subject credential lookup

Use Steward's minted subject contract, keeping acting-user email and runtime UID distinct. Give Bob matching tool authority so his request reaches the real credential broker and proves Alice's token is not returned; retain a separate unauthorized subject to assert policy denial precedes credential resolution.

* fix: report latest conformance as informational

Keep the latest-upstream conformance step and logs visibly failed, but tolerate that specific step and record the finding as a workflow warning and job summary. Pinned CI and setup failures remain blocking.
@lbelyaev
lbelyaev merged commit 4f54c94 into main Jul 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant