Skip to content
IAM Insights

Explainers · Glossary

Workload Identity Credential

Workload Identity Credential, in the IETF WIMSE framework: a signed credential (typically a JWT or X.509 certificate) that a workload presents to prove which workload it is.

In our briefings

The claim each of the newest briefings on Workload Identity Credential would have you leave with.

  1. Iyer's IBM Research team builds agent identity from standards that already exist and keeps the plumbing out of the agent. SPIRE attests each workload and issues it a SPIFFE credential. The workload presents that credential to the OAuth provider, Keycloak in their setup, where workloads used to hold a static secret, and the provider checks it against the SPIFFE side before it issues a signed, expiring access token. In the open-source Rossoctl project, a sidecar called Cortex intercepts the agent's inbound and outbound traffic and fetches both credentials, because changing every agent and tool, she says, is "not the application developer's job." Her explanation of the token, which carries a user ID and an application ID, uses a browser login as the example; nowhere in the episode does she say how an agent's token comes to carry the user's ID as well as its own.

    IBM Research puts agent identity in a SPIFFE and OAuth sidecar; Maia Iyer calls authorization policy still openBI-FIND-2026-1515

  2. The IETF's workload-identity architecture does not give AI agents an identity type of their own. Its one passage on them says 'AI intermediaries are a special case of delegated workloads': an agent is software that inherits the security context of whoever called it and SHOULD pass that context on unless it has been authorized to reduce it. The one line it draws is between acting for someone and acting alone. Actions an agent takes that cannot be attributed to a principal MUST be clearly distinguished from delegated ones, for example with a separate workload identity or different token scopes. Vendors argue over whether agents are a third kind of identity; the standards text treats them as workloads with a caller.

    The IETF's workload-identity architecture gives AI agents one subsection, calling an agent a delegated workloadBI-FIND-2026-0298

Cited in 2 briefings

Every briefing that discusses this term, newest first.

  1. IBM Research puts agent identity in a SPIFFE and OAuth sidecar; Maia Iyer calls authorization policy still open

    Podcast · · Kubernetes Bytes · Your AI Agent Has Too Much Access | Fixing Agent Identity · Sep 15, 2026

  2. The IETF's workload-identity architecture gives AI agents one subsection, calling an agent a delegated workload

    Draft · · IETF Datatracker · Joseph Salowey et al. · Jul 6, 2026