Scalr

Runs authenticate as the workspace they ran in.

What proves the identity

The token has to come from https://scalr.io, and its scalr_workspace_id claim has to match the workload you named. penv compares that claim byte for byte, with no wildcards.

scalr_workspace_id is matched rather than sub, because this platform puts something per run in sub.

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

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:

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

The snippet the console prints

# In a Scalr custom hook (pre-plan or pre-apply): a Scalr run executes no other shell.
# Shell variable SCALR_OIDC_AUD = YOUR_WORKSPACE_ID, at WORKSPACE level:
# set at environment level it hands every workspace in that environment one audience.
# The token is exported for the whole run phase; there is no narrower path.
T="$SCALR_OIDC_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.

Related

• Machine identity
• Connect a Platform in the console
• Scalr documentation, where the value people get wrong is always the subject