Ona
Environments authenticate as the project they were created from.
Environments authenticate as the project they were created from.
Identity proof
The token has to come from https://app.gitpod.io, 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 |
|---|---|---|---|
| Organization ID | 0199a1b2-c3d4-4e5f-8a9b-0c1d2e3f4a5b | no | Needs V3 token configuration, since a V2 organization's subject has another shape. |
| Project ID | 0199f0e1-d2c3-4b4a-9857-6d5e4f3a2b1c | no | Every environment created from this project matches. |
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://app.gitpod.io |
| Claim compared | sub |
| Subject | organization_id:0199a1b2-c3d4-4e5f-8a9b-0c1d2e3f4a5b:project_id:0199f0e1-d2c3-4b4a-9857-6d5e4f3a2b1c |
| Identity name | ona-6d5e4f3a2b1c |
We name the identity for you, so the form never asks for one.
Console snippet
T=$(ona idp token --audience YOUR_WORKSPACE_ID)
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
- Ona documentation: the subject is the value most often set wrong