Skip to content
IAM Insights

Explainers · Glossary

Trust domain (workload identity)

trust domains

The administrative boundary that issues and vouches for workload identities, named by an organization's domain; a verifier decides which trust domains it accepts.

In our briefings

What our briefings say about Trust domain (workload identity) itself, with the most direct claims first.

  1. A SPIFFE trust domain name has no registrar behind it. The core specification calls these names "nominally self-registered": no delegating authority ties a name to a legal entity, and there is no technical means of stopping two trust domains from using the same one. Each domain has its own root of trust, so when names collide the spec says identity claims from one fail validation in the other and the two cannot federate (connect to one another). It advises a registered domain name as a suffix, or a random name such as a UUID when names are generated automatically. We read the name as a label: a relying party tells two domains apart by the root it has chosen to trust, and the name alone says nothing about who runs the domain.

    SPIFFE trust domain names have no registrar, and the core spec warns that roles in a credential can go staleBI-FIND-2026-2081

  2. The -09 WIMSE text redefines a trust domain as an administrative scope for workload identities and adds rules for keeping domains apart. Revision -08 said a trust domain maps to trust anchors; -09 says each relying party MUST associate a trust domain with the issuers authorized for it and their trust anchors, and MUST validate a credential using only the trust anchors of the domain named in its workload identifier, subject to each issuer's and key's configured scope. A new Trust Domain Separation section warns that this check does not help when one key is trusted for several domains: "If the same private signing key is authorized to issue credentials for multiple trust domains, compromise of that key permits forgery of credentials for all of those domains." Different issuer names do not restore the separation. Separate intermediate CAs under a common root can limit each one's issuing authority if relying parties enforce constraints such as name constraints, but the root remains a shared dependency. Isolation, the draft says, needs separate signing keys and enforceable domain-specific limits on issuing authority.

    IETF draft: AI agents you need to audit or revoke separately should not share one identityBI-FIND-2026-2443

  3. Across trust domains, the draft offers delegation_chain as the form for the claims transcription that the OAuth working group's identity-chaining draft leaves undefined, and the receiving server MUST copy the chain into the token it issues. It then gives two accounts of who signs the upstream records. Section 8.3 has resource servers verify each record with the key of the server that issued it, which "may differ across records"; section 10.7 says the receiving server re-signs the upstream records, so every record verifies with the current issuer's key. We read these as two different tokens, and the draft does not say which a resource server should expect.

    A June OAuth draft logs each hand-off between AI agents, but the per-hop limits the act claim lacks are optionalBI-FIND-2026-1289

›Cited in 14 briefings

Every briefing that discusses this term, newest first.

  1. IETF draft: AI agents you need to audit or revoke separately should not share one identity

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

  2. AAuth gives every agent its own key, then keeps the delegation chain out of the token on purpose

    Draft · · IETF Datatracker · Dick Hardt, Hellō · Sep 25, 2026

  3. Transaction Tokens carry who started a request through internal services and define no list of the hops in between

    Draft · · IETF OAuth Working Group · Atul Tulshibagwale et al. · Jul 30, 2026

  4. OAuth's draft for crossing trust domains is approved for publication and never says agent

    Draft · · IETF OAuth Working Group · Arndt Schwenkschuster et al. · Jul 19, 2026

  5. SPIFFE trust domain names have no registrar, and the core spec warns that roles in a credential can go stale

    Article · · SPIFFE project (GitHub) · SPIFFE project · Jul 1, 2026

  6. WIMSE's agent draft adds how an agent's access ends and where policy engines fit, without a new requirement

    Draft · · IETF WIMSE Working Group · Pieter Kasselman et al. · Sep 15, 2026

  7. A cross-domain transaction-token grant now names AI agents as a use and keeps the call chain at home

    Draft · · IETF Datatracker · George Fletcher et al. · Sep 10, 2026

  8. The IETF names workloads with a URI on the owner's domain; revision -04 pins down how two names are compared

    Draft · · IETF Datatracker · Yaroslav Rosomakho et al. · Oct 23, 2026

  9. An IETF draft says agent access checks may refuse when a source is down, but must not record that as a 'no'

    Draft · · IETF Datatracker · Girish Konda · Oct 19, 2026

  10. An OAuth profile for AI agents makes every hand-off cut privileges, but a shorter expiry alone counts as a cut

    Draft · · IETF Datatracker · Angel Cruz · Feb 7, 2026

  11. Batch delegation assigns each permission to an agent, then filters at token exchange

    Draft · · IETF Datatracker · Yuan Ni et al. · Jul 3, 2026

  12. A June OAuth draft logs each hand-off between AI agents, but the per-hop limits the act claim lacks are optional

    Draft · · IETF Datatracker · Dapeng Liu et al. · Jun 8, 2026

  13. Atlassian's first draft for offline delegation banned bearer handles; revision 05 just recommends sender binding

    Draft · · IETF Datatracker · Larry Zhu et al. · May 22, 2026

  14. State Farm moved SPIRE from many token issuers to one, then hit an AWS key quota and a 15-character name limit

    Video · · CNCF [Cloud Native Computing Foundation] · Nov 24, 2025