Skip to content
IAM Insights

Explainers · Glossary

OAuth SPIFFE Client Authentication

draft-ietf-oauth-spiffe-client-auth · SPIFFE client authentication

An IETF OAuth working-group draft that lets a workload log in to an OAuth authorization server with its SPIFFE identity (a JWT, WIT or X.509 certificate) instead of a client secret.

reference →

In our briefings

The claim each of the newest briefings on OAuth SPIFFE Client Authentication would have you leave with.

  1. Under revision -11 of the bis draft, a JWT that authenticates an OAuth client has exactly one permitted audience. The draft rewrites RFC 7523's rule so that the audience 'MUST use the issuer identifier [RFC8414] of the authorization server as its sole value', 'the token endpoint URL of the authorization server MUST NOT be used as an audience value', and the server 'MUST reject any JWT that does not contain its issuer identifier as its sole audience value'. Unless an application profile says otherwise, the values are compared by Simple String Comparison. The server must have an issuer identifier to use the rule at all, and participants no longer need to agree on audience identifiers for client authentication. Pushed authorization requests (RFC 9126) get the same sole-issuer rule. The draft's reason is that endpoint addresses other than the issuer 'cannot be directly validated' and, sent to a different endpoint, 'can open an attack vector'. It cites the vulnerability University of Stuttgart researchers disclosed to the working group in January 2025, and their paper on audience injection attacks.

    The JWT an agent or other OAuth client signs in with may name only the server's issuer, never the token endpointBI-FIND-2026-0350

  2. OAuth's attestation draft (ATTEST, revision -12), as McGuinness cites it, puts trust in attesters outside its scope and gives a client no way to name them. His draft has the client do the naming: it publishes a client_attesters list, entries of an issuer and a key-set URL, in its registered metadata or its Client ID Metadata Document. The server accepts an attestation only when two things hold: the client's current metadata endorses that issuer, and the server's own policy permits that attester for that client. In his words, "Endorsement alone does not make an attester trusted". The server checks that the attestation's subject is exactly the client_id and ignores jku, x5u, x5c and embedded keys when it selects a key. If the server has configured its own key source for that issuer, that source governs the issuer for every client, and the endorsed URL is compared but not fetched. If it has not, keys can come from the endorsed URL where the server lets the publisher choose them. Publishing the list does not force a client to attest. The draft says the parameter "does not itself require attestation", so an attacker that obtains the client's other credentials can authenticate without one unless the deployment requires attestation, through an attestation-based authentication method or server policy. Under RFC 7592, a registration access token can change the client's authentication method or keys even where it cannot change the list, so the draft says a deployment relying on endorsement also restricts those changes or requires attestation by server policy.

    An OAuth client gets to name who vouches for it, and removing one waits on server cachesBI-FIND-2026-0657

  3. Under this draft a client's identity is a web address and whatever its owner publishes there. The client_id is an https URL, which revision -03 says "MUST contain a path component other than /", and the JSON document at that URL "MUST contain a client_id property whose value MUST match" it. The authorization server learns the client's name, redirect addresses and keys by fetching that document. Its security section says a client that changes its URL is "a brand new client with no relationship to the previous one", and that losing control of the domain would let a third party "assume the client's identity". We read this as a name anyone can look up. That is more than an anonymous registration gives a server, though it says nothing about what software sits behind the name.

    OAuth's URL client ID draft tightens server rules in -03; the client is still whoever controls the URLBI-FIND-2026-0319

›Cited in 8 briefings

Every briefing that discusses this term, newest first.

  1. The JWT an agent or other OAuth client signs in with may name only the server's issuer, never the token endpoint

    Draft · · IETF Datatracker · Michael B. Jones et al. · Apr 28, 2026

  2. An OAuth client gets to name who vouches for it, and removing one waits on server caches

    Draft · · IETF Datatracker · Karl McGuinness · Sep 28, 2026

  3. OAuth's URL client ID draft tightens server rules in -03; the client is still whoever controls the URL

    Draft · · IETF Datatracker · Aaron Parecki et al. · Jul 6, 2026

  4. OAuth's SPIFFE draft opens metadata URLs to all three credentials and says what a self-served key cannot prove

    Draft · · IETF Datatracker · Arndt Schwenkschuster et al. · Jun 15, 2026

  5. An agent audit draft says the agent is not trusted, yet lets the agent's operator run the audit store

    Draft · · IETF Datatracker · Mirja Kühlewind et al. · Sep 7, 2026

  6. An attested OAuth client is one somebody vouched for; revision 12 says to trust its claims only as far as the voucher

    Draft · · IETF Datatracker · Tobias Looker et al. · Oct 13, 2026

  7. SPIFFE can authenticate an OAuth client; trust and registration still come first

    Draft · · IETF Datatracker · Arndt Schwenkschuster et al. · Oct 3, 2025

  8. RFC 7591 asks OAuth servers to accept clients with no token, and calls their signed statements self-asserted

    Article · · RFC Editor · Justin Richer et al. · Jul 9, 2015

Related terms

What appears alongside OAuth SPIFFE Client Authentication in the same briefings.

KeycloakSPIFFEJWT Bearer GrantAssertion Framework for OAuth 2.0 Client Authentication and Authorization GrantsJWT-SVIDmTLSX.509-SVIDOAuth Attestation-Based Client Authentication