Client Attester
Client Attester
In OAuth attestation-based client authentication, the backend party that vouches for a client instance and its key by issuing a signed Client Attestation.
In our briefings
The claim each of the newest briefings on Client Attester would have you leave with.
Under revision 12, an attested client is one whose attester signed for its key. The Client Attestation JWT must carry four claims: the client identifier, an expiry, an issue time (optional until this revision) and the client instance's public key. What would make 'attested' say something about the software stays optional and undefined. The JWT 'is generally understood to convey' that the attester verified the instance's authenticity and integrity, which 'might encompass statements about its software and hardware environment', and it may describe properties of the key, such as hardware-backed storage, or other characteristics of the instance, such as (new in revision 12) the criteria or policy it was evaluated against. The draft defines no claim for any of these, puts the evidence and how it is collected out of scope, and lets a client with no backend do the attester's job itself. A new Section 12.3 says every claim in the JWT, integrity included, is an assertion by the attester, and that a server 'should rely on such claims only to the extent that it trusts the issuing Client Attester'.
An attested OAuth client is one somebody vouched for; revision 12 says to trust its claims only as far as the voucherBI-FIND-2026-0361
Cited in 1 briefing
Every briefing that discusses this term, newest first.
- 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