Skip to content

Add registry revocations endpoint - #40

Merged
jvanulde merged 1 commit into
jvanulde:mainfrom
edip-dev-01:fix/issue-24-revocations-endpoint
Jul 3, 2026
Merged

Add registry revocations endpoint#40
jvanulde merged 1 commit into
jvanulde:mainfrom
edip-dev-01:fix/issue-24-revocations-endpoint

Conversation

@edip-dev-01

Copy link
Copy Markdown
Contributor

What Problem This Solves

Issue #24 asks the registry to serve revocations per issuer. PR #39 created signed revocations.json files and local CLI enforcement, but the registry had no way to publish or fetch those lists.

Why This Change Was Made

This adds issuer-scoped revocation list storage to the registry and CLI helpers so revocation checks can use registry-hosted signed lists.

User Impact

  • Registry publishers can upload signed revocation lists with qcap publish-revocations.
  • Consumers can fetch issuer lists with qcap fetch-revocations.
  • qcap open can verify against a registry-hosted list using --revocations-url.
  • The demo now proves a revoked capability is blocked through the registry endpoint.

Evidence

  • go test ./... in services/qcap-registry
  • cargo check --workspace
  • cargo test -p qcap-cli
  • powershell -ExecutionPolicy Bypass -File scripts/demo.ps1

Fixes #24

@jvanulde
jvanulde merged commit 854f18f into jvanulde:main Jul 3, 2026
2 checks 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.

Revocations endpoint (#srv-006)

2 participants