Sample code for 30+ languages & platforms
JavaScript

Use a PEM TLS Client Certificate

See more SMTP Examples

Demonstrates the Chilkat MailMan.SetSslClientCertPem method, which sets the client-side certificate for SSL/TLS connections, loading it from PEM data or from a PEM file. The first argument may contain the PEM text itself or a path to a PEM file; the second is the PEM password. This example loads the client certificate from a PEM file.

Background: PEM is the familiar Base64 text format bracketed by -----BEGIN CERTIFICATE----- lines, and a single PEM can hold both a certificate and its (optionally encrypted) private key. It is the common format in Unix/OpenSSL environments, whereas PFX is more typical on Windows. Because this method accepts either the PEM text or a filename, you can supply credentials straight from a config value or secret store without writing them to disk.
Note
This example is intended for running within a Chilkat.Js embedded JavaScript engine. All Chilkat JavaScript examples require Chilkat v11.4.0 or greater.
JavaScript
var success = false;

//  Demonstrates the MailMan.SetSslClientCertPem method, which sets the client-side
//  certificate for SSL/TLS connections, loading it from PEM data or from a PEM file.  The
//  1st argument may contain PEM text or a PEM file path; the 2nd is the PEM password.

var mailman = new CkMailMan();

//  Configure the SMTP server connection.
mailman.SmtpHost = "smtp.example.com";
mailman.SmtpPort = 465;
mailman.SmtpSsl = true;
mailman.SmtpUsername = "user@example.com";
mailman.SmtpPassword = "myPassword";

//  Load the client certificate from a PEM file.
success = mailman.SetSslClientCertPem("qa_data/certs/client.pem","pem_password");
if (success == false) {
    console.log(mailman.LastErrorText);
    return true;
}

success = mailman.VerifySmtpLogin();
if (success == false) {
    console.log(mailman.LastErrorText);
    return true;
}

console.log("Connected using a PEM TLS client certificate.");

//  Note: The path "qa_data/certs/client.pem" is a relative local filesystem path,
//  relative to the current working directory of the running application.