I think there's probably some confusion here:
1. "Certificate Pinning" is a technique whereby a client verifies that the certificate coming from the server
is a specific certificate (or chains to a specific root). Pinning can present problems for Fiddler's HTTPS interception because the pinning checks will usually fail when they find Fiddler's interception certificates.
2. Client Certificates are certificates that the client sends to the server
to identify itself. Use of client certificates requires extra work in Fiddler because you need to tell Fiddler which certificate to send to the server. Fiddler can send a client certificate to the server by specifying the local filename of that certificate in the https-Client-Certificate
Now, I'm guessing that maybe you're in a different scenario: Maybe you're saying: "I have the server's certificate and private key, and I would like to use Fiddler to use that so that the client's certificate pinning check does not fail." If that's the case, you can use the StoreCert
method: please see this example
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items