Sample code for 30+ languages & platforms
JavaScript Requires Chilkat v10.1.2+

Secure FTP with Client Certificate

See more FTP Examples

Chilkat FTP2 provides the ability to use a client certificate with secure FTP (implicit or explicit SSL/TLS). This example demonstrates how to load a certificate from a .pfx and use it as the client-side SSL cert. Note: Client-side certificates are only needed in situations where the server demands one.
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;

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

var ftp = new CkFtp2();

ftp.Hostname = "ftp.example.com";
ftp.Port = 21;
ftp.Username = "test";
ftp.Password = "test";

//  This example will use explict TLS/SSL.
//  Establish an explicit secure channel after connection
//  on the standard FTP port 21.
ftp.AuthTls = true;

//  The Ssl property is for establishing an implicit SSL connection
//  on port 990.  Because this example uses explicit SSL, it 
//  should remain false.
ftp.Ssl = false;

//  Load a certificate from a .pfx
//  A PFX may contain several certs, including the certificates
//  in a chain of authority.
var certStore = new CkCertStore();
var password;
password = "***";
//  Load the certs from a PFX into an in-memory certificate store:
success = certStore.LoadPfxFile("chilkat.pfx",password);
if (success !== true) {
    console.log(certStore.LastErrorText);
    return;
}

//  Find the desired certificate.
var jsonCN = new CkJsonObject();
jsonCN.UpdateString("CN","cert common name");

var cert = new CkCert();
success = certStore.FindCert(jsonCN,cert);
if (success == false) {
    console.log("Certificate not found!");
    return;
}

//  Use this certificate for our secure (SSL/TLS) connection:
success = ftp.SetSslClientCert(cert);

//  Connect and login to the FTP server.  The connection is 
//  made secure because of the AuthTls setting.
success = ftp.Connect();
if (success !== true) {
    console.log(ftp.LastErrorText);
    return;
}
else {
    //  LastErrorText contains information even when
    //  successful. This allows you to visually verify
    //  that the secure connection actually occurred.
    console.log(ftp.LastErrorText);
}

console.log("Secure FTP Channel Established!");

//  Do whatever you're doing to do ...
//  upload files, download files, etc...

//  .....
//  .....

success = ftp.Disconnect();