> This page is for Workload Identity, version v1.16.0-rc.5.
> For other versions, use one of these documentation indexes:
> - Latest · v1.16.0-rc.7 (default): https://docs.nvidia.com/workload-identity/v1.16.0-rc.7/llms.txt
> - v1.16.0-rc.5: https://docs.nvidia.com/workload-identity/v1.16.0-rc.5/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/workload-identity/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/workload-identity/_mcp/server.

# NVIDIA Workload Identity

NVIDIA Workload Identity turns shard-local SPIRE identities into DSX JWTs that
relying parties can validate across shards. An identity shard contains an
independent SPIRE deployment and a co-located NVIDIA Workload Identity Keys
deployment. NVIDIA Workload Identity Keys validates only its local SPIRE
JWT-SVIDs, issues DSX JWTs, and distributes its public signing keys through
the external DSX Event Bus.

There is no SPIRE federation between shards. Cross-shard trust starts after
token exchange, when another shard or relying party validates a DSX JWT with
the aggregate public keys served by any NVIDIA Workload Identity Keys
instance.

## User guide

See the [examples user guide](/workload-identity/v1.16.0-rc.5/user-guide/examples) to acquire and consume DSX
JWTs through token-fetcher injection or the DSX IMDS endpoint.

Component commands and runtime configuration:

- [NVIDIA Workload Identity Controller](/workload-identity/v1.16.0-rc.5/components/identity-controller)
- [DSX IMDS Network Setup](/workload-identity/v1.16.0-rc.5/components/imds-network-setup)
- [`dsx_imds` NodeAttestor agent plugin](/workload-identity/v1.16.0-rc.5/components/node-attestor-agent)
- [`dsx_imds` NodeAttestor server plugin](/workload-identity/v1.16.0-rc.5/components/node-attestor-server)
- [`dpu_hw` NodeAttestor server plugin](https://github.com/NVIDIA/doca-platform/tree/545320feb894f20577fa0abf6885c6aafc4fb2eb/cmd/dpu-hw-server)
- [DSX Token Fetcher](/workload-identity/v1.16.0-rc.5/components/token-fetcher)
- [NVIDIA Workload Identity Keys Proxy CSI Driver](/workload-identity/v1.16.0-rc.5/components/keys-proxy-csi-driver)
- [Generate Signing Keyset](/workload-identity/v1.16.0-rc.5/components/generate-signing-keyset)
- [DSX IMDS](/workload-identity/v1.16.0-rc.5/components/imds)
- [NVIDIA Workload Identity Keys](/workload-identity/v1.16.0-rc.5/components/identity-keys)
- [Kata UDS Proxy](/workload-identity/v1.16.0-rc.5/components/kata-uds-proxy)

### SPIRE upgrades

Before upgrading SPIRE, check its
[upgrade requirements](https://github.com/spiffe/spire/blob/main/doc/upgrading.md)
for supported version skew, upgrade order, and configuration changes.

## Deployment

Install [`charts/dsx-identity`](/workload-identity/v1.16.0-rc.5/charts/dsx-identity) once per identity
shard with Helm. When enabled, the parent chart creates DPF DPUService resources
that reference the [DSX IMDS](/workload-identity/v1.16.0-rc.5/charts/dsx-imds) and
[DPU token-fetcher admission](/workload-identity/v1.16.0-rc.5/charts/dsx-token-fetcher) child charts.