Zig Requires Chilkat v11.0.0+
Zig
Accept TLS Connection with Client Authentication
See more Socket/SSL/TLS Examples
Demonstrates how to accept a TLS connection requiring client authentication. This is the case where the TLS client sends a certificate. It is also known as "Two-Way SSL".Chilkat Zig Downloads
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 listen_ssl_socket = try chilkat.Socket.init();
defer listen_ssl_socket.deinit();
// An SSL/TLS server needs a digital certificate. This example loads it from a PFX file.
// Note: This is the server's certificate.
const cert = try chilkat.Cert.init();
defer cert.deinit();
// The 1st argument is the file path, the 2nd arg is the
// PFX file's password:
cert.loadPfxFile("chilkat.pfx", "test") catch {
std.debug.print("{s}\n", .{try cert.getLastErrorText(alloc)});
return;
};
// To accept client client certificates in the TLS handshake,
// we must indicate a list of acceptable client certificate root CA DN's
// that are allowed. (DN is an acronym for Distinguished Name.)
// Call AddSslAcceptableClientCaDn once for each acceptable CA DN.
// Here are a few examples so you can see the general format of a DN.
listen_ssl_socket.addSslAcceptableClientCaDn("C=SE, O=AddTrust AB, OU=AddTrust External TTP Network, CN=AddTrust External CA Root") catch {};
listen_ssl_socket.addSslAcceptableClientCaDn("O=Digital Signature Trust Co., CN=DST Root CA X3") catch {};
// Use the certificate:
listen_ssl_socket.initSslServer(cert) catch {
std.debug.print("{s}\n", .{try listen_ssl_socket.getLastErrorText(alloc)});
return;
};
// Bind and listen on a port:
const my_port = 8123;
// Allow for a max of 5 queued connect requests.
const back_log = 5;
listen_ssl_socket.bindAndListen(my_port, back_log) catch {
std.debug.print("{s}\n", .{try listen_ssl_socket.getLastErrorText(alloc)});
return;
};
// If accepting an SSL/TLS connection, the SSL handshake is part of the connection
// establishment process. This involves a few back-and-forth messages between the
// client and server to establish algorithms and a shared key to create the secure
// channel. The sending and receiving of these messages are governed by the
// MaxReadIdleMs and MaxSendIdleMs properties. If these properties are set to 0
// (and this is the default unless changed by your application), then the
// AcceptNext can hang indefinitely during the SSL handshake process.
// Make sure these properties are set to appropriate values before calling AcceptNext.
// Set a 10 second max for waiting to read/write. This is for the SSL/TLS handshake establishment.
listen_ssl_socket.setMaxReadIdleMs(10000);
listen_ssl_socket.setMaxSendIdleMs(10000);
// Accept a single client connection and establish the secure SSL/TLS channel:
const max_wait_millisec = 20000;
const client_sock = try chilkat.Socket.init();
defer client_sock.deinit();
listen_ssl_socket.acceptNext(max_wait_millisec, client_sock) catch {
std.debug.print("{s}\n", .{try listen_ssl_socket.getLastErrorText(alloc)});
return;
};
// The client (in this example) is going to send a "Hello Server! -EOM-"
// message. Read it:
const received_msg = client_sock.receiveUntilMatch(alloc, "-EOM-") catch {
std.debug.print("{s}\n", .{try client_sock.getLastErrorText(alloc)});
return;
};
std.debug.print("{s}\n", .{received_msg});
// Send a "Hello Client! -EOM-" message:
client_sock.sendString("Hello Client! -EOM-") catch {
std.debug.print("{s}\n", .{try client_sock.getLastErrorText(alloc)});
return;
};
// Close the connection with the client
// Wait a max of 20 seconds (20000 millsec)
try client_sock.close(20000);
}