OpenID Connect Dynamic Client Registration
Mechanism for sender-constraining OAuth 2.0 tokens via a proof-of-possession mechanism on the application level which allows for the detection of replay attacks with tokens.
- from
- OpenID Connect
- added
- 2026-10-10
- likes
- 0
similar
-
OAuth 2.0 Dynamic Client Registration Protocol datatracker.ietf.org
Defines how an OAuth 2.0 Relying Party (RP) can dynamically register with the OAuth 2.0 server provider.
-
OAuth 2.0 Demonstrating Proof of Possession (DPoP) datatracker.ietf.org
Demonstrates proof of possession of the client's private key for OAuth 2.0.
-
OAuth 2.0 Dynamic Client Registration Management Protocol datatracker.ietf.org
Endpoints for management of OAuth 2.0 dynamic client registrations.
-
OAuth 2.0 Attestation-Based Client Authentication datatracker.ietf.org
Extension to OAuth 2.0 enabling public clients to authenticate using key-bound attestations.
-
OpenID Provider Authentication Policy Extension 1.0 openid.net
Specifications about a mechanism by which a Relying Party can request that particular authentication policies like multi-factor authentication be applied by the OpenID Provider.
-
OpenID Connect Discovery 1.0 openid.net
Mechanism for an OpenID Connect Relying Party to discover the End-User's OpenID Provider and obtain information needed to interact with it.
OpenID Connect › Resources > Specifications > Published: “Mechanism for sender-constraining OAuth 2.0 tokens via a proof-of-possession mechanism on the application level which allows for the detection of replay attacks with tokens.”