React Native Requires Chilkat v10.1.2+
React Native
Upload to Tumbleweed SecureTransport FTPS Server
See more FTP Examples
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.Chilkat React Native Downloads
import { Cert, CertStore, Ftp2, JsonObject } from '@chilkat/react-native'
async function chilkatExample() {
// This example requires the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.
const ftp = new Ftp2();
// 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.
const certStore = new CertStore();
const password = '***';
// Load the certs from a PFX into an in-memory certificate store:
try {
certStore.loadPfxFile('my.pfx', password);
} catch {
console.log(certStore.lastErrorText);
return;
}
// Find the desired certificate.
const jsonCN = new JsonObject();
jsonCN.updateString('CN', 'cert common name');
const cert = new Cert();
try {
certStore.findCert(jsonCN, cert);
} catch {
console.log('Certificate not found!');
return;
}
// Tell the Chilkat FTP2 component to use the client-side
// cert for the SSL connection:
ftp.setSslClientCert(cert);
// Connect and authenticate with the FTP server.
try {
await ftp.connectAsync();
// LastErrorText contains information even when
// successful. This allows you to visually verify
// that the secure connection actually occurred.
console.log(ftp.lastErrorText);
} catch {
console.log(ftp.lastErrorText);
return;
}
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.
try {
await ftp.changeRemoteDirAsync('someSubDir');
} catch {
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.
const localFilename = 'someFile.dat';
const remoteFilename = 'someFile.dat';
// Upload the file.
try {
await ftp.putFileAsync(localFilename, remoteFilename);
} catch {
console.log(ftp.lastErrorText);
return;
}
await ftp.disconnectAsync();
}