Skip to content

fix(installer): transitional artifact identity allowlist for org migration - #13

Draft
tnunamak wants to merge 1 commit into
mainfrom
tim/transitional-artifact-identities
Draft

fix(installer): transitional artifact identity allowlist for org migration#13
tnunamak wants to merge 1 commit into
mainfrom
tim/transitional-artifact-identities

Conversation

@tnunamak

Copy link
Copy Markdown
Contributor

Every consumer of the pinned installer currently fails verification deterministically: the connectors-latest index is signed by this repo's workflow (post-migration), but the artifacts it references still carry vana-com-signed Sigstore bundles (artifactUrls still point at vana-com releases). One hardcoded identity can't verify both.

Change

  • Index verification unchanged: strict PDP-Connect identity only
  • Artifact verification: ordered TRANSITIONAL_ARTIFACT_CERTIFICATE_IDENTITIES allowlist — PDP-Connect first, historic vana-com fallback; failure only after all attempts, error lists every attempted identity

Verified

Unit tests (fallback success / all-fail reporting / strict index) plus a live check against the published release: index verified PDP, vana-signed github-playwright@1.2.0 verified via fallback and unpacked. All repo check scripts pass.

Retirement condition

Re-publish every referenced artifact from this repo's workflow; when the index references no vana-com-signed artifact, shrink the allowlist to one entry.

Context: unblocks vana-com/context-gateway#238 (connectors:check cannot pass with any consumer-side configuration today).

…ation

The connectors-latest index is now signed by this repository's
publish-connector-release-index.yml workflow, but the artifacts it
references still carry Sigstore bundles from the pre-migration
vana-com/data-connectors workflow. Verifying both against the single
hardcoded identity deterministically fails for every consumer.

- index verification stays strict: PDP-Connect identity only
- artifact verification tries TRANSITIONAL_ARTIFACT_CERTIFICATE_IDENTITIES
  in order (PDP-Connect, then the historic vana-com identity) and fails
  only after all attempts, reporting every attempted identity
- tests: vana-com fallback success, all-identity failure message,
  strict index verification

Retirement: once every referenced artifact is re-published with
PDP-Connect bundles, shrink the allowlist back to one entry.

Signed-off-by: Tim Nunamaker <tnunamak@gmail.com>
@github-actions

Copy link
Copy Markdown

Schema Health Check — All Clear

All 50 scopes have consistent local schema files.

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