OAuth Attestation-Based Client Authentication
draft-ietf-oauth-attestation-based-client-auth · Client Attestation PoP JWT
An IETF OAuth draft where a client proves its identity to the token endpoint with an attestation issued by a trusted party plus a fresh proof-of-possession token signed by the client's own key.
In our briefings
The claim each of the newest briefings on OAuth Attestation-Based Client Authentication would have you leave with.
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
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
A key that a client serves from its own Client ID Metadata Document proves less than the SPIFFE ID it carries. When an authorization server takes the bundle address from the document, whoever controls the client_id URL picks the keys, so a successful login shows, in the draft's words, "that the client holds a key vouched for by that party, not that the trust domain named in spiffe_id issued the SVID." Its example is a document at attacker.example that claims spiffe://bank.example/payments. Section 6.1 binds such a bundle to that one client, so the attacker can sign in only as itself. The server must not treat the ID as issued by bank.example in authorization policy, token claims or introspection, unless the bundle came as section 6 describes or the trust domain is bound to the client_id host.
OAuth's SPIFFE draft opens metadata URLs to all three credentials and says what a self-served key cannot proveBI-FIND-2026-2023
›Cited in 8 briefings
Every briefing that discusses this term, newest first.
- 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
- 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
- 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
- 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
- An OAuth draft lets device checks set an app's scopes; a first review found a copied app could reuse the result
Draft · · IETF Datatracker · Efe Kahraman, Mekarge · Jun 9, 2026
- OAuth's in-app login draft lets a native app collect the password itself, and leaves each server to vet the app
Draft · · IETF Datatracker · Aaron Parecki et al. · Feb 28, 2026
- OpenID's credential issuance standard is OAuth for wallets, and assumes a trusted wallet is an app on a phone
Article · · OpenID Foundation · Torsten Lodderstedt et al. · Sep 16, 2025
- An OAuth client that never registers: the July 2025 draft makes its URL the identity and leaves most server checks as SHOULDs
Draft · · IETF Datatracker · Aaron Parecki et al. · Jul 23, 2025
Related terms
What appears alongside OAuth Attestation-Based Client Authentication in the same briefings.
OAuth SPIFFE Client AuthenticationPushed Authorization RequestsClient ID Metadata DocumentsOAuth 2.0 Authorization Server MetadataOpenID FederationDefakto