(C#) Use Installed Cert on Windows for TLS Client Authentication

Demonstrates how to use a certificate that has already been installed on a Windows PC for TLS client authentication.

Chilkat .NET Downloads Chilkat .NET Framework Chilkat for .NET Core

//  This example requires the Chilkat API to have been previously unlocked.
//  See Global Unlock Sample for sample code.

Chilkat.Http http = new Chilkat.Http();

bool success;

//  On Windows, a pre-installed certificate can be loaded in a number of different ways.
//  This example loads by the common name:
Chilkat.Cert cert = new Chilkat.Cert();
bool success = cert.LoadByCommonName("My ECA Medium Assurance Identity Certificate");
if (success != true) {
    Debug.WriteLine(cert.LastErrorText);
    return;
}

//  Make sure this certificate has a private key available.
//  It should be a private key such that when the certificate was installed, it was marked as "exportable"
//  so that authorized programs are able to access the private key.
if (cert.HasPrivateKey() != true) {
    Debug.WriteLine("A private key is needed for TLS client authentication.");
    Debug.WriteLine("This certificate has no private key.");
    return;
}

//  Set the certificate to be used for mutual TLS authentication
//  (i.e. sets the client-side certificate for two-way TLS authentication)
success = http.SetSslClientCert(cert);
if (success != true) {
    Debug.WriteLine(http.LastErrorText);
    return;
}

//  At this point, the HTTP object instance is setup with the client-side cert, and any SSL/TLS
//  connection will automatically use it if the server demands a client-side cert.