How do GitLab CI id_tokens work for cloud login?
GitLab CI id_tokens give a job a short signed token a cloud can verify. Learn aud, the sub format, ref_protected and why project_id beats names.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
GitLab CI id_tokens give a job a short signed token a cloud can verify. Learn aud, the sub format, ref_protected and why project_id beats names.
Org owners can view and revoke fine-grained GitHub tokens but not classic ones, and SSH keys made by a token keep working. Here is the leaver sequence.
Set the default GITHUB_TOKEN to read-only for repository contents, raise it per job, and know that fork pull requests get a read-only token regardless.
The sub claim in GitHub's OIDC token changes with environment, branch, tag, and pull request jobs. See each format and how to write a tight trust rule.
With restrictions on, members cannot authorize OAuth apps for org data and unapproved apps lose private access. Defaults, approval flow, what to check.
GitHub environments can require reviewers, block self-review and limit branches before a deploy job runs. Setup steps for gating infrastructure applies.
Environment secrets reach only jobs that use the environment, after its rules pass. Add deployment branch rules and reviewers to guard production secrets.
Set up a federated identity credential on a Microsoft Entra app so GitHub Actions can deploy to Azure with no stored secret. Steps, subjects, limits.
A run can restore caches from its own branch and the default branch, but not sibling branches. The scope rules, what they imply, and how to use them.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.