(JavaScript) Upload to Tumbleweed SecureTransport FTPS Server
Demonstrates how to connect, authenticate, and upload file to a Tumbleweed Secure Transport SSL FTP Server. Instead of providing a login name and password, you pass the string "site-auth" for the username, and an empty string for the password. You must also provide a client-side digital certificate -- as the certificate's credentials and validity are used to authenticate. Note: This example requires Chilkat v10.1.2 or greater.
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();
// This code has been tested with the Tumbleweed server
// at sft.wellsfargo.com
ftp.Hostname = "sft.wellsfargo.com";
// Use these exact strings for the username and password:
ftp.Username = "site-auth";
ftp.Password = "";
// Establish an AUTH SSL secure channel after connecting.
// Your client-side certificate is used for authentication when
// the SSL channel is established.
ftp.AuthSsl = true;
// The Ssl property is for establishing an implicit SSL connection
// on port 990. Do not set it.
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 = "***";
// Load the certs from a PFX into an in-memory certificate store:
success = certStore.LoadPfxFile("my.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;
}
// Tell the Chilkat FTP2 component to use the client-side
// cert for the SSL connection:
success = ftp.SetSslClientCert(cert);
// Connect and authenticate with the FTP server.
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!");
// Change to the remote directory where the file will be
// uploaded. If your file is to be uploaded to the FTP user
// account's home directory, this is not necessary.
success = ftp.ChangeRemoteDir("someSubDir");
if (success !== true) {
console.log(ftp.LastErrorText);
return;
}
// You may include an absolute or relative path with the
// local filename. If no path is included, the file should
// be present in the current working directory of the calling
// process.
var localFilename = "someFile.dat";
var remoteFilename = "someFile.dat";
// Upload the file.
success = ftp.PutFile(localFilename,remoteFilename);
if (success !== true) {
console.log(ftp.LastErrorText);
return;
}
success = ftp.Disconnect();
|