PingFederate
Services authenticate with the PingFederate client they run as.
Services authenticate with the PingFederate client they run as.
Identity proof
The token has to come from https://sso.acme.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 |
|---|---|---|---|
| PingFederate URL | https://sso.acme.com | no | The base URL discovery names as its issuer. Must be reachable from the internet. |
| Client ID | penv-deployer | no | Every machine using this client 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://sso.acme.com |
| Claim compared | sub |
| Subject | penv-deployer |
| Identity name | pingfed-penv-deployer |
We name the identity for you, so the form never asks for one.
Console snippet
# PingFederate: a JSON Web Token access token manager with instance id penv, where
# Issuer Claim Value = your PingFederate URL, exactly
# Audience Claim Value = YOUR_WORKSPACE_ID
# Use Centralized Signing Key (or Publish Keys to the PingFederate JWKS Endpoint), RS256
# with sub added to its Access Token Attribute Contract, used by this client alone, and an
# access token mapping for Client Credentials that fulfils sub from Context: ClientId.
# Ask for this audience and no other. A token requested for two audiences fails every exchange.
# $PING_CLIENT_SECRET is this client's own secret, already on the machine.
T=$(printf 'grant_type=client_credentials&client_id=%s&client_secret=%s&access_token_manager_id=penv' \
"$PING_CLIENT_ID" "$PING_CLIENT_SECRET" \
| curl -sS https://<PINGFEDERATE_HOST>/as/token.oauth2 --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 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
- PingFederate documentation: the subject is the value most often set wrong