Zig

Load Default Certificate from Smart Card or Token

See more Certificates Examples

Chilkat contains internal logic to examine a connected smart card or USB token, and will make decisions based on make/model to successfully interact with the hardware. When faced with a new smartcard or token, the best starting point is to call LoadFromSmartcard with an empty string argument to see what Chilkat discovers. Zig

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

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

    const cert = try chilkat.Cert.init();
    defer cert.deinit();

    // If you know the smart card PIN, it's good to set it prior to loading from the smartcard/USB token.
    cert.setSmartCardPin("12345678");

    // To let Chilkat discover what smartcard or token is connected, pass an empty string to LoadFromSmartcard.
    // When testing in this way, it's best to have only a single smartcard or token connected to the system.
    cert.loadFromSmartcard("") catch {
        std.debug.print("{s}\n", .{try cert.getLastErrorText(alloc)});
        std.debug.print("Certificate not loaded.\n", .{});
        return;
    };

    // The LastErrorText property on all Chilkat objects will contain
    // information even when the method call is successful.
    // You can examine the LastErrorText to see what Chilkat found and
    // what decisions were made.
    //
    // For example, if a certificate was successfully loaded via LoadFromSmartcard,
    // but then signing failed, such as w/ Pdf, XmlDSig, CAdES, etc.,
    // then we would want to examine the LastErrorText from the call to
    // LoadFromSmartcard to get detailed information about the card.
    std.debug.print("{s}\n", .{try cert.getLastErrorText(alloc)});

    std.debug.print("Found: {s} serial={s}\n", .{ try cert.getSubjectDN(alloc), try cert.getSerialNumber(alloc) });
}