Pushed authorization request with client attestation and PKCE
OID4VCI 1.0 §RFC 9126 Sections 2 and 4MUSTRoles: issuer, authorization_server
Requirement as recorded in the ProtocolSoup registry
A pushed authorization request is client-attestation authenticated, PKCE-bound, and represented by a short-lived request_uri bound to the exact client and redirect URI. An optional PAR DPoP binding is retained, while HAIP wallets may introduce DPoP at token redemption. Authorization Server Metadata advertises the enforced client-attestation authentication and signing algorithms.
Read §RFC 9126 Sections 2 and 4 in OID4VCI 1.0Self-test verdict
PassCommit 97df6a8Evaluated
This is ProtocolSoup's result against its own implementation at the commit shown. It is not a certification of ProtocolSoup or of any other product.
Tests
- TestPushedAuthorizationRequestBindsAttestationDPoPAndCredentialDetails
./internal/protocols/oid4vci
Pass - TestAuthorizationServerMetadataAdvertisesAttestationWhenConfigured
./internal/protocols/oid4vci
Pass