GitHub Actions

Workflows authenticate with the repository and ref they ran from.

Identity proof

The token has to come from https://token.actions.githubusercontent.com, and its sub claim has to match the workload you named. We compare that claim byte for byte, with no wildcards.

Every token also has to name your workspace as its audience. Ask for this audience and no other. A token requested for two audiences fails every exchange.

Console fields

A repository, then the project and environment this identity reaches, the role it gets, and whether a branch or a GitHub environment may authenticate. We read the subject from GitHub, so no form asks for one.

Trust

For the repository you pick:

We name the identity for you, so the form never asks for one.

Console snippet

permissions:
  id-token: write          # without this, no token is issued at all
# We refuse pull_request_target runs: trigger this job on push or pull_request.

steps:
  - run: |
      T=$(curl -sS \
        -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" \
        "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=YOUR_WORKSPACE_ID" | jq -r .value)
      C=$(T="$T" jq -n '{token:env.T}' | curl -sS "https://penv.cloud/api/v1/auth/oidc" \
        -H 'content-type: application/json' --data-binary @- | jq -r .credential)
      PENV_TOKEN="$C" penv pull

The snippet finishes with penv pull, which writes a file. We recommend penv run for a process; penv pull is for a host that needs a file on disk. Connect your CI has the wrapped step.

Related

• Machine identity
• Connect a Platform in the console
• GitHub Actions
• GitHub Actions documentation: the subject is the value most often set wrong