Every SM caller needs a token. Which auth method mints that token depends on where the caller runs. All syntax below is stock Vault CLI — TigerTrust’s compat surface implements the same endpoints.

Method matrix

CallerMethodNotes
Developer laptopoidc (browser)Federated via workspace SSO
CI runner (GitHub Actions, GitLab, Buildkite)jwtOIDC token issued by the CI provider
Kubernetes podkubernetesServiceAccount JWT
Generic Linux host / VMapprolerole_id + secret_id pair
AWS EC2 / ECS / LambdaawsInstance/task identity
Azure VM / AKSazureManaged identity
GCP VM / GKEgcpWorkload identity

AppRole

vault auth enable approle
vault write auth/approle/role/prod-app \
  token_policies=prod-read \
  token_ttl=1h token_max_ttl=24h \
  token_bound_cidrs=10.0.0.0/8

ROLE_ID=$(vault read -format=json auth/approle/role/prod-app/role-id | jq -r .data.role_id)
SECRET_ID=$(vault write -f -format=json auth/approle/role/prod-app/secret-id | jq -r .data.secret_id)

vault write auth/approle/login role_id="$ROLE_ID" secret_id="$SECRET_ID"

Kubernetes

vault auth enable kubernetes
vault write auth/kubernetes/config \
  kubernetes_host=https://kubernetes.default.svc \
  kubernetes_ca_cert=@ca.crt

vault write auth/kubernetes/role/prod-app \
  bound_service_account_names=prod-app \
  bound_service_account_namespaces=prod \
  policies=prod-read ttl=1h
In the pod (using vault agent):
env:
  - name: VAULT_ADDR
    value: https://api.tigertrust.io
# vault-agent config points at auth/kubernetes/login with role=prod-app

JWT / OIDC (CI)

vault auth enable jwt
vault write auth/jwt/config \
  oidc_discovery_url=https://token.actions.githubusercontent.com

vault write auth/jwt/role/prod-deploy \
  role_type=jwt \
  user_claim=sub \
  bound_claims='{"repository":"org/repo","ref":"refs/heads/main"}' \
  policies=prod-deploy ttl=15m
Then in GitHub Actions:
- uses: hashicorp/vault-action@v3
  with:
    url: https://api.tigertrust.io
    method: jwt
    role: prod-deploy
    secrets: |
      secret/data/prod/api-key value | API_KEY

Cloud IAM

Each cloud method binds a token to a specific IAM identity. See Settings → Secrets Manager → Auth Methods for the exact config per cloud.

Policies

Policies attached to tokens minted by these methods.

Engines

What those tokens can access once minted.