No explainer written for this spec yet. The summary, relations and documented support below are maintained.
A client instance authenticates with an attestation from its backend plus a proof of possession, for apps that cannot keep a secret.
Attestation-Based Client Authentication
A client instance authenticates with an attestation from its backend plus a proof of possession, for apps that cannot keep a secret.
- Where it stands
- WG last call or write-up
- Documented support
- 0
- Activity
- 0
How it relates to other specs
Relations diagram
flowchart LR s_attestation_client_auth["Attestation-Based Client Authentication"] s_oauth2["OAuth 2.0"] s_spiffe_client_auth["OAuth SPIFFE Client Authentication"] style s_attestation_client_auth stroke-width:3px s_attestation_client_auth -->|Extends| s_oauth2 s_spiffe_client_auth -->|Profiles| s_attestation_client_auth
Documented support
Adoption lists only support stated in official documentation (the vendor's or project's own, or a standards body's page naming it), and a weekly check confirms the cited phrase is still on that page. Experimental, alpha and beta support is counted separately as preview.
No sourced support entries collected yet. This says nothing about how widely it is used.
Activity
Revisions from the Datatracker, explanations from this site's daily runs, and mailing-list subjects naming the draft.
Nothing collected about this spec yet.