Zig

Use Installed Cert on Windows for TLS Client Authentication

See more HTTP Examples

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

const std = @import("std");
const chilkat = @import("chilkat");

pub fn main(init: std.process.Init) !void {
    const alloc = init.arena.allocator();

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

    const http = try chilkat.Http.init();
    defer http.deinit();

    // On Windows, a pre-installed certificate can be loaded in a number of different ways.
    // This example loads by the common name:
    const cert = try chilkat.Cert.init();
    defer cert.deinit();
    cert.loadByCommonName("My ECA Medium Assurance Identity Certificate") catch {
        std.debug.print("{s}\n", .{try cert.getLastErrorText(alloc)});
        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()) {
        std.debug.print("A private key is needed for TLS client authentication.\n", .{});
        std.debug.print("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)
    http.setSslClientCert(cert) catch {
        std.debug.print("{s}\n", .{try http.getLastErrorText(alloc)});
        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.
}