FAPI 2.0
FAPI 2.0 with mTLS
The same profile, proven by the certificate of the connection.
Client
not registered yet
Forged: FAPI 2.0 with mTLS
Registered at the provider the first time it runs (RFC 7591)
{ "client_name": "Forged: FAPI 2.0 with mTLS", "token_endpoint_auth_method": "self_signed_tls_client_auth", "scope": ["profile","email"], "response_mode": "jwt", "authorization_signed_response_alg": "ES256", "pushed": true, "require_pushed_authorization_requests": true, "request_object_signing_alg": "ES256", "token_binding": "mtls", "tls_client_certificate_bound_access_tokens": true, "id_token_signed_response_alg": "ES256", "frontchannel_logout": true}
The provider does not offer "self_signed_tls_client_auth" for "token_endpoint_auth_method": it offers "client_secret_basic", "client_secret_post", "private_key_jwt", "client_secret_jwt", "none".
Proof
Run it: every step it takes is ticked here.