DPoP (RFC 9449)
Official docs outline
6 sections- Objectives
Binding access and refresh tokens to a client key.
- DPoP proof JWTs
htm, htu, jti, iat, ath claims and the dpop+jwt type.
- DPoP access token request
Presenting a DPoP proof at the token endpoint.
- Protected resource access
DPoP authorization scheme and token binding checks.
- Authorization server nonce
Nonce challenges to bound proof lifetimes.
- Security considerations
Proof replay, theft and key storage.
Each section links to the official page. Titles and summaries by Extra Credit; the docs belong to their authors.
More in Auth and identity
All 21- FIDO2 CTAP 2.1
- JSON Web Encryption (RFC 7516)
- JSON Web Key and Algorithms (RFC 7517 and 7518)
- JSON Web Signature (RFC 7515)
- JSON Web Token (RFC 7519)
- Kerberos V5 (RFC 4120)
- LDAP (RFC 4510 series)
- OAuth 2.0 (RFC 6749)
- OAuth 2.0 Bearer Token Usage (RFC 6750)
- OAuth 2.0 Device Authorization Grant (RFC 8628)
- OAuth 2.0 Security Best Current Practice (RFC 9700)
- OAuth 2.0 Token Exchange (RFC 8693)