HashiCorp Nomad

Tasks authenticate with the workload identity Nomad signs for their job.

Identity proof

The token has to come from https://nomad.acme.com, and its nomad_job_id claim has to match the workload you named. We compare that claim byte for byte, with no wildcards.

nomad_job_id is matched rather than sub, which on this platform does not name the workload in a form you can pin.

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
Nomad issuer URL	`https://nomad.acme.com`	no	The `oidc_issuer` in your server block, reachable from the internet.
Job ID	`api`	no	A job with this id in another namespace matches too.

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://nomad.acme.com`
Claim compared	`nomad_job_id`
Subject	`api`
Identity name	`nomad-api`

We name the identity for you, so the form never asks for one.

Console snippet

identity {
  name = "penv"
  # Ask for this audience and no other. A token requested for two audiences fails every exchange.
  aud  = ["YOUR_WORKSPACE_ID"]
  file = true
  ttl  = "1h"
}

# in the task:
#   T=$(cat "$NOMAD_SECRETS_DIR/nomad_penv.jwt")
#   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 pull

The 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.

Machine identity
Connect a Platform in the console
HashiCorp Nomad documentation: the subject is the value most often set wrong

Identity proof

Console fields

Trust

Console snippet

Related

On this page