Tcl Requires Chilkat v10.1.2+

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. Tcl

load ./chilkat.dll

set success 0

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

set ftp [new_CkFtp2]

#  This code has been tested with the Tumbleweed server
#  at sft.wellsfargo.com
CkFtp2_put_Hostname $ftp "sft.wellsfargo.com"

#  Use these exact strings for the username and password:
CkFtp2_put_Username $ftp "site-auth"
CkFtp2_put_Password $ftp ""

#  Establish an AUTH SSL secure channel after connecting.
#  Your client-side certificate is used for authentication when
#  the SSL channel is established.
CkFtp2_put_AuthSsl $ftp 1

#  The Ssl property is for establishing an implicit SSL connection
#  on port 990.  Do not set it.
CkFtp2_put_Ssl $ftp 0

#  Load a certificate from a .pfx
#  A PFX may contain several certs, including the certificates
#  in a chain of authority.
set certStore [new_CkCertStore]

set password "***"
#  Load the certs from a PFX into an in-memory certificate store:
set success [CkCertStore_LoadPfxFile $certStore "my.pfx" $password]
if {$success != 1} then {
    puts [CkCertStore_lastErrorText $certStore]
    delete_CkFtp2 $ftp
    delete_CkCertStore $certStore
    exit
}

#  Find the desired certificate.
set jsonCN [new_CkJsonObject]

CkJsonObject_UpdateString $jsonCN "CN" "cert common name"

set cert [new_CkCert]

set success [CkCertStore_FindCert $certStore $jsonCN $cert]
if {$success == 0} then {
    puts "Certificate not found!"
    delete_CkFtp2 $ftp
    delete_CkCertStore $certStore
    delete_CkJsonObject $jsonCN
    delete_CkCert $cert
    exit
}

#  Tell the Chilkat FTP2 component to use the client-side
#  cert for the SSL connection:
set success [CkFtp2_SetSslClientCert $ftp $cert]

#  Connect and authenticate with the FTP server.
set success [CkFtp2_Connect $ftp]
if {$success != 1} then {
    puts [CkFtp2_lastErrorText $ftp]
    delete_CkFtp2 $ftp
    delete_CkCertStore $certStore
    delete_CkJsonObject $jsonCN
    delete_CkCert $cert
    exit
} else {
    #  LastErrorText contains information even when
    #  successful. This allows you to visually verify
    #  that the secure connection actually occurred.
    puts [CkFtp2_lastErrorText $ftp]
}

puts "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.
set success [CkFtp2_ChangeRemoteDir $ftp "someSubDir"]
if {$success != 1} then {
    puts [CkFtp2_lastErrorText $ftp]
    delete_CkFtp2 $ftp
    delete_CkCertStore $certStore
    delete_CkJsonObject $jsonCN
    delete_CkCert $cert
    exit
}

#  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.
set localFilename "someFile.dat"
set remoteFilename "someFile.dat"

#  Upload the file.
set success [CkFtp2_PutFile $ftp $localFilename $remoteFilename]
if {$success != 1} then {
    puts [CkFtp2_lastErrorText $ftp]
    delete_CkFtp2 $ftp
    delete_CkCertStore $certStore
    delete_CkJsonObject $jsonCN
    delete_CkCert $cert
    exit
}

set success [CkFtp2_Disconnect $ftp]

delete_CkFtp2 $ftp
delete_CkCertStore $certStore
delete_CkJsonObject $jsonCN
delete_CkCert $cert