FAPI 2.0
FAPI 2.0 with DPoP
Pushes a signed request, reads a signed response, holds a token bound to its key.
Client
JC6zyTTaIc69lswo6_sNt0-6Kn…
Forged: FAPI 2.0 with DPoP
Registered at the provider the first time it runs (RFC 7591)
{ "client_name": "Forged: FAPI 2.0 with DPoP", "token_endpoint_auth_method": "private_key_jwt", "scope": ["profile","email"], "response_mode": "jwt", "authorization_signed_response_alg": "ES256", "pushed": true, "require_pushed_authorization_requests": true, "request_object_signing_alg": "ES256", "require_signed_request_object": true, "token_binding": "dpop", "dpop_signing_alg": "ES256", "id_token_signed_response_alg": "ES256", "id_token_encrypted_response_alg": "RSA-OAEP-256", "userinfo_signed_response_alg": "ES256", "userinfo_encrypted_response_alg": "RSA-OAEP-256", "frontchannel_logout": true, "backchannel_logout": true}
Proof
Run it: every step it takes is ticked here.