Docs
Reference

GitLab CI

Jobs authenticate with the project and ref they ran from.

Jobs authenticate with the project and ref they ran from.

What proves the identity

The token has to come from https://gitlab.com, and its sub claim has to match the workload you named. penv compares 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.

What the console asks for

FieldExampleAdvancedWhat it pins
Project pathacme/apinoThe group and project from your project's URL.
BranchmainnoOnly jobs on this branch authenticate.
GitLab hosthttps://gitlab.comyesSelf-managed installs use their own URL, and must be reachable from the internet.
Ref typebranchyesOne of Branch, Tag.

A field marked advanced carries a default and stays behind the disclosure until you open it.

The console also asks which project and environment this identity reaches and which role it gets, with the credential lifetime behind Advanced.

What the trust holds

Built from the example answers above:

WhatValue
Issuerhttps://gitlab.com
Claim comparedsub
Subjectproject_path:acme/api:ref_type:branch:ref:main
Identity namegitlab-acme-api-main

penv names the identity for you, so the form never asks for one.

The snippet the console prints

pull-secrets:
  id_tokens:
    PENV_ID_TOKEN:
      aud: YOUR_WORKSPACE_ID
  script:
    - |
      T="$PENV_ID_TOKEN"
      C=$(curl -sS "https://penv.cloud/api/v1/auth/oidc" \
        -H 'content-type: application/json' \
        -d "{\"token\":\"$T\"}" | jq -r .credential)
      PENV_TOKEN="$C" penv pull

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