Workload identity
Issue short-lived OIDC tokens to pipeline workloads so they can authenticate to any OIDC-compatible system without connector-managed credentials.
Harness acts as a workload identity provider for pipeline workloads, issuing short-lived, signed OIDC ID tokens that carry execution context. External systems validate these tokens through public OIDC discovery and JWKS endpoints, then grant access based on the claims the token carries.
In this section
Workload identity overview: Understand how Harness issues tokens and how they differ from connector OIDC.
Subject templates: Customize the subject claim in OIDC tokens.
Token claims reference: Execution context claims that identify which workload requested the token.
Configure OIDC discovery URL in your provider: Register Harness as an OIDC identity provider in AWS, GCP, Azure, or Vault.
Last updated
Was this helpful?