Skip to content

docs(authz): feedback PEP (subject-proving) design + plan - #81

Draft
phoebus-84 wants to merge 2 commits into
docs/cross-service-authzfrom
docs/authz-feedback
Draft

phoebus-84 wants to merge 2 commits into
docs/cross-service-authzfrom
docs/authz-feedback

Conversation

@phoebus-84

Copy link
Copy Markdown
Collaborator

Stacked on #79 (cross-service authz design + contract vectors). Adds the feedback PEP (subject-proving) design and TDD plan for the second service wired to the cross-service PDP.

What's here

  • docs/cross-service-authz-feedback-design.md — the feedback service trusts a self-asserted x-user-id header (the reverse proxy forwards it verbatim), so any valid signer can act as any user. The Zenflows PDP re-verifies the signature and returns the proven Person.id; feedback writes under it. Ownership rules stay in feedback SQL. Enforce-now; server-side only (no GUI/SDK/proxy change).
  • docs/cross-service-authz-feedback-plan.md — 6-task TDD plan across the zenflows PDP and the feedback service.

See the stacked implementation PRs: zenflows feat/authz-feedback-pdp and interfacer-feedback-service feat/authz-pep.

🤖 Generated with Claude Code

phoebus-84 and others added 2 commits October 15, 2026 11:36
Second service wired to the cross-service PDP. Feedback trusts a
self-asserted x-user-id header (the proxy forwards it verbatim), so a
valid signer can act as any user. The PDP re-verifies the signature and
returns the proven Person.id; feedback writes under it and treats
x-user-id as non-authoritative. Ownership rules stay in feedback SQL.
Enforce now; server-side only, no GUI/SDK/proxy change.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
6-task TDD plan across zenflows PDP (feedback action family + proven
subject, transport binding relaxation) and the feedback service (pure
authz package, PDP client, AuthzMiddleware, wiring). Global constraints,
5-item Review Focus, full code per step.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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