buildOne report1 publisher In a dev.to write-up, Jorge RN traces the chain from a workload's own identity to an ephemeral OCI session token, where the authorization decision reads claims such as repository, workflow and branch.
Reality
- Evidence30
- Adoption
- Insufficient
- Hype gap+25
- Incentives40
- Confidence35
buildOne report1 publisher A release workflow signed provenance, reached sigstore, then took a 404 on a package its owner has published for months. The registry withholds existence on purpose, so the real fault, a runner bundling npm 10.8.2, never appears in the error.
Reality
- Evidence74
- Adoption18
- Hype gap+5
- Incentives22
- Confidence66
buildOne report1 publisher Build configurations can now authenticate to AWS and Google Cloud without stored keys, provided you accept that the TeamCity server holds the signing key and that rotating it leaves already-issued tokens valid.
Reality
- Evidence46
- Adoption12
- Hype gap+14
- Incentives82
- Confidence56
buildOne report1 publisher Workload Identity Federation swaps a downloadable JSON key for three objects that all have to exist before anything works. An InfoQ practitioner reports 120-plus GCP projects on it in six months, and names the gate teams leave open.
Reality
- Evidence42
- Adoption48
- Hype gap+8
- Incentives35
- Confidence46
buildOne report1 publisher One practitioner's account of moving three Jenkins fleets onto AssumeRoleWithWebIdentity lists the same mistakes every time, and two of them leave the build lights green.
Reality
- Evidence38
- Adoption
- Insufficient
- Hype gap+12
- Incentives28
- Confidence44