Broker/store must mint signed repo-scoped artifact claims #17

Open
opened 2026-07-05 20:43:06 +00:00 by stephen · 0 comments
Owner

Companion to #15 and PR #16's CHANGES review.

The action-side fix verifies RASTER_ARTIFACTS_SCOPE_CLAIM and derives the artifact prefix from the signed repository claim, but production still needs a trusted issuer outside the workflow job:

  • The Forgejo runner, broker, or store front-end must mint RASTER_ARTIFACTS_SCOPE_CLAIM for the actual run repository before job steps execute.
  • The private signing key must never be exposed to workflow-controlled env or repository secrets. Jobs receive only the claim and the public verification key.
  • The claim should include at least repository; include exp and run metadata if available.
  • Store credentials or policy should be narrowed to the same repository prefix where possible, so the signed claim and backend policy agree.

Without this issuer/store half, a deployment cannot provide the signed claim required by the action and should keep #15 open for production rollout tracking.

Companion to #15 and PR #16's CHANGES review. The action-side fix verifies `RASTER_ARTIFACTS_SCOPE_CLAIM` and derives the artifact prefix from the signed `repository` claim, but production still needs a trusted issuer outside the workflow job: - The Forgejo runner, broker, or store front-end must mint `RASTER_ARTIFACTS_SCOPE_CLAIM` for the actual run repository before job steps execute. - The private signing key must never be exposed to workflow-controlled env or repository secrets. Jobs receive only the claim and the public verification key. - The claim should include at least `repository`; include `exp` and run metadata if available. - Store credentials or policy should be narrowed to the same repository prefix where possible, so the signed claim and backend policy agree. Without this issuer/store half, a deployment cannot provide the signed claim required by the action and should keep #15 open for production rollout tracking.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rasterstate/download-artifact-action#17
No description provided.