ci: publish SBOMs via OIDC trusted publishing instead of API tokens - #28
Draft
aurangzaib048 wants to merge 1 commit into
Draft
ci: publish SBOMs via OIDC trusted publishing instead of API tokens#28aurangzaib048 wants to merge 1 commit into
aurangzaib048 wants to merge 1 commit into
Conversation
Switch the staging and production upload jobs in sbomify.yaml from static API token auth to GitHub OIDC trusted publishing: drop TOKEN (SBOMIFY_STAGE_TOKEN / SBOMIFY_TOKEN) and set OIDC_AUDIENCE (stage.sbomify.com / sbomify.com). Both jobs already declare `permissions: id-token: write`; COMPONENT_ID, API_BASE_URL and all other inputs are unchanged.
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
1 participant
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.
Draft — part of the org-wide migration of our own SBOM uploads from API tokens to GitHub OIDC trusted publishing.
What changed
sbomify.yaml— both upload jobs switch fromTOKENto OIDC (both already hadpermissions: id-token: write):upload-sbom-staging: dropSBOMIFY_STAGE_TOKEN, setOIDC_AUDIENCE: stage.sbomify.com(keepsAPI_BASE_URL: https://stage.sbomify.com)upload-sbom-production: dropSBOMIFY_TOKEN, setOIDC_AUDIENCE: sbomify.comCOMPONENT_IDand all other inputs unchanged.sbomify/py-libtea→rw6sHZjLbrDbXt5ZkVk3DSSTVerify after merge
A master push runs staging; a tag runs production. Confirm each binding's "Last used" flips, then retire the token secrets here.