(Unicode 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 C/C++ Library Downloads
MS Visual C/C++ Linux/CentOS C/C++ Alpine Linux C/C++ MAC OS X C/C++	armhf/aarch64 C/C++ C++ Builder iOS C/C++ Android C/C++	Solaris C/C++ MinGW C/C++

#include <CkHttpW.h>
#include <CkCertW.h>

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

    CkHttpW 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:
    CkCertW cert;
    bool success = cert.LoadByCommonName(L"My ECA Medium Assurance Identity Certificate");
    if (success != true) {
        wprintf(L"%s\n",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) {
        wprintf(L"A private key is needed for TLS client authentication.\n");
        wprintf(L"This certificate has no private key.\n");
        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) {
        wprintf(L"%s\n",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.
    }