Reference
Teleport Workload Identity
Workloads authenticate with the SPIFFE ID Teleport issues them through tbot.
Workloads authenticate with the SPIFFE ID Teleport issues them through tbot.
What proves the identity
The token has to come from https://acme.teleport.sh/workload-identity, and its sub claim has to match the workload you named. penv compares 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.
What the console asks for
| Field | Example | Advanced | What it pins |
|---|---|---|---|
| Proxy URL | https://acme.teleport.sh | no | Your Proxy Service public address, reachable from the internet. |
| SPIFFE ID | spiffe://acme.teleport.sh/svc/api | no | The trust is exactly as narrow as this ID. |
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:
| What | Value |
|---|---|
| Issuer | https://acme.teleport.sh/workload-identity |
| Claim compared | sub |
| Subject | spiffe://acme.teleport.sh/svc/api |
| Identity name | teleport-acme-teleport-sh-svc-api |
penv names the identity for you, so the form never asks for one.
The snippet the console prints
# tbot.yaml
services:
- type: workload-identity-jwt
# Ask for this audience and no other. A token requested for two audiences fails every exchange.
audiences: ["YOUR_WORKSPACE_ID"]
destination: { type: directory, path: /opt/machine-id }
selector: { name: penv }
# in the workload:
# T=$(cat /opt/machine-id/jwt_svid)
# C=$(curl -sS "https://penv.cloud/api/v1/auth/oidc" \Related
- Machine identity
- Connect a Platform in the console
- Teleport Workload Identity documentation, where the value people get wrong is always the subject