fix(rbac): grant frontend read access to PurchaseRequest + RegistrationRequest#540
Closed
bussyjd wants to merge 1 commit into
Closed
fix(rbac): grant frontend read access to PurchaseRequest + RegistrationRequest#540bussyjd wants to merge 1 commit into
bussyjd wants to merge 1 commit into
Conversation
…onRequest Without these rules, the frontend ServiceAccount got 403 from the Kubernetes API when /api/marketplace/purchases tried to list PurchaseRequests cluster-wide, surfacing as 'Failed to list PurchaseRequests' on the My Purchases page and an empty rows count even when the agent had signed authorizations. Adds read-only (get/list/watch) on: - purchaserequests + status (agent owns writes via x402 skill) - registrationrequests + status (controller owns writes) Stacked on feat/marketplace-bundle (#536) where this template lives.
Collaborator
Author
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two read-only RBAC rules to the frontend ClusterRole so /api/marketplace/purchases and registration-status badges work without 403s.
Bug discovered during validation
Running the bundle (#536) deployment + visiting
/marketplace/purchasesproduced:Frontend pod logs:
The existing ClusterRole (
obol-frontend-openclaw-discovery) granted CRUD on ServiceOffers but nothing for PurchaseRequests or RegistrationRequests — both of which the marketplace UI lists cluster-wide for the "purchases paying to this wallet" and "ERC-8004 registered" badges.Fix
Read-only is sufficient: the agent owns PurchaseRequest writes via the buy-x402 skill; the controller owns RegistrationRequest writes.
Stack
Stacked on
feat/marketplace-bundle(#536) whereinternal/embed/infrastructure/base/templates/obol-frontend.yamllives. Merge after #536.Test plan
/api/marketplace/purchasesreturns 200, My Purchases page renders rows with chevron drawer expansion (validated via Chrome MCP).