GitLab CI
Jobs authenticate with the project and ref they ran from.
Jobs authenticate with the project and ref they ran from.
Identity proof
The token has to come from https://gitlab.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
| Field | Example | Advanced | What it pins |
|---|---|---|---|
| Project path | acme/api | no | The group and project from your project's URL. |
| Branch | main | no | Only jobs on this branch authenticate. |
| GitLab host | https://gitlab.com | yes | Self-managed installs use their own URL, and must be reachable from the internet. |
| Ref type | branch | yes | One 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.
Trust
Built from the example answers above:
| What | Value |
|---|---|
| Issuer | https://gitlab.com |
| Claim compared | sub |
| Subject | project_path:acme/api:ref_type:branch:ref:main |
| Identity name | gitlab-acme-api-main |
We name the identity for you, so the form never asks for one.
Console snippet
pull-secrets:
id_tokens:
PENV_ID_TOKEN:
aud: YOUR_WORKSPACE_ID
script:
- |
T="$PENV_ID_TOKEN"
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 pullThe 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
- GitLab CI
- GitLab CI documentation: the subject is the value most often set wrong