[ Web Proxy ]
URL:
Viewing: https://docs.chainloop.dev/guides/github-keyless [Back]  [Original]

Keyless Attestations in GitHub - Chainloop Documentation
Skip to main content

Keyless Attestations in GitHub

How to configure Chainloop attestations from GitHub Actions without using Chainloop API tokens.

This feature is only available on Chainloops platform paid plans.
You can perform attestations from GitHub Actions without using Chainloop API tokens. This removes token management from your workflows and helps you align with SLSA 3 checks by default. To achieve this youll need to:
  • Connect your GitHub repository to a project
  • Configure workflow permissions for OIDC

1 - Connect your GitHub repository to a project

Before attesting, connect the Chainloop GitHub integration and link the repository to a project:
Attestations from repositories that are not connected to a project will not be accepted.

2 - Configure the workflow for keyless attestation

You can leverage GitHub OIDC tokens directly from your workflow. Keep the workflow configuration simple and include these permissions:
An example workflow:
Do not set CHAINLOOP_TOKEN in your workflow environment. In keyless mode, the CLI automatically requests a GitHub OIDC token and uses it to authenticate with Chainloop no manual token configuration needed.
If you have onboarded the same repository to more than one Chainloop organization, pass the --org flag to the init command:
How to trace AI coding sessions
Keyless Attestations in GitLab

Web Proxy Viewer  |  New URL  |  Original Page