> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/harness-platform/use-harness-platform/pipelines/workload-identity.md).

# 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](https://developer.harness.io/harness-platform/use-harness-platform/pipelines/workload-identity/workload-identity-overview.md): Understand how Harness issues tokens and how they differ from connector OIDC.
* [Subject templates](https://developer.harness.io/harness-platform/use-harness-platform/pipelines/workload-identity/subject-templates.md): Customize the subject claim in OIDC tokens.
* [Token claims reference](https://developer.harness.io/harness-platform/use-harness-platform/pipelines/workload-identity/token-claims-reference.md): Execution context claims that identify which workload requested the token.
* [Configure OIDC discovery URL in your provider](https://developer.harness.io/harness-platform/use-harness-platform/pipelines/workload-identity/configure-oidc-url.md): Register Harness as an OIDC identity provider in AWS, GCP, Azure, or Vault.
