Repository navigation
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This branch has not been deployed
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.
Description
Document repository-scoped Docker OIDC authentication for Docker Hardened Image pulls and private attestation reads. Update the DHI use, verification, and customization guides, and link the verification workflow from OIDC connection setup.
The GitHub Actions example exchanges a GitHub identity token for a short-lived Docker access token, masks it, authenticates regctl to Docker Hub and the Scout registry through stdin, reads a manifest and lists attestations, then signs out. Explain the organization username, repository grants, token expiry, direct dhi.io repository mapping, and the distinction between pulling customized images and managing customization definitions.
The automatic OIDC exchange in docker/login-action applies to Docker Hub; setting its registry input to dhi.io or the Scout registry does not perform that exchange.
Validation: formatted and checked all four changed pages with the repository-pinned rumdl 0.2.49 and Vale 3.17.0. No errors or warnings on added lines; three warnings and one suggestion remain in unchanged text. Added source links and anchors resolve. The extracted workflow passes actionlint 1.7.12, YAML/JavaScript/shell syntax checks, and local checks for token masking, stdin-only credentials, failed exchanges, missing access tokens, failed registry login, and cleanup. GitHub, Docker Identity, and registry IO are explicitly faked in the workflow checks. Verified the exchange contract against docker/login-action v4.5.0 and the client arguments against regctl v0.8.2 source. Full Hugo/HTML validation is left to CI.
Related issues or tickets
DXT-1716
Reviews
Keep this PR as a draft until the associated backend changes are released and the workflow is verified with a real GitHub-issued identity token and Docker OIDC connection. Local implementation/client checks do not establish deployed support or a successful live provider exchange.
Technical and product review must confirm repository resource selection for direct dhi.io grants (
dhi/<image>) in Docker Home and validate both direct DHI and mirrored/customized-image attestation paths. The workflow demonstrates reads only; it does not document OIDC access to customization management or general Scout organization APIs.