Keycloak

Services authenticate with the Keycloak client they run as.

What proves the identity

The token has to come from https://sso.acme.com/realms/prod, and its azp claim has to match the workload you named. penv compares that claim byte for byte, with no wildcards.

azp 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

# Client → Client scopes → dedicated → Add mapper → Audience: YOUR_WORKSPACE_ID
# Then turn OFF Full scope allowed there, or remove the roles scope: its audience-resolve
# mapper otherwise adds `account` and the token arrives with two audiences.
# Ask for this audience and no other. A token requested for two audiences fails every exchange.
# $KEYCLOAK_CLIENT_SECRET is this client's own secret, already on the machine.
T=$(printf 'grant_type=client_credentials&client_id=%s&client_secret=%s' \
  "$KEYCLOAK_CLIENT_ID" "$KEYCLOAK_CLIENT_SECRET" \
  | curl -sS <ISSUER>/protocol/openid-connect/token --data-binary @- | jq -r .access_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
• Keycloak documentation, where the value people get wrong is always the subject