(DataFlex) Using WS_FTP Self-signed Certificate file (.crt) and Private Key File. (.key)

Demonstrates how to use a self-signed certificate created by WS_FTP with Chilkat FTP2.

Note: It is usually not necessary for the FTP client to use a client-side certificate. Most FTP servers using SSL and TLS connections (explicit or implicit) do not require client-side certs. In addition, some high-security FTP servers require "real" certificates -- meaning certificates issued by a real certificate authority with a chain of authentication that leads to a trusted root certificate. The certificates created by WS_FTP are self-signed and untrusted.

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

Use ChilkatAx-win32.pkg

Procedure Test
    Handle hoFtp
    Handle hoCertStore
    Boolean iSuccess
    Variant vCert
    Handle hoCert
    String sTemp1
    Boolean bTemp1

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

    // Important:  Before running this program, convert your
    // .crt and .key files to a .p12 using OpenSSL:
    // The command is this:
    // openssl pkcs12 -export -in test.crt -inkey test.key -out test.p12
    // 

    Get Create (RefClass(cComChilkatFtp2)) To hoFtp
    If (Not(IsComObjectCreated(hoFtp))) Begin
        Send CreateComObject of hoFtp
    End

    Set ComHostname Of hoFtp To "ftp.***.com"
    Set ComPort Of hoFtp To 21
    Set ComUsername Of hoFtp To "testLogin"
    Set ComPassword Of hoFtp To "testPassword"

    // This example will use explict TLS/SSL.
    // Establish an explicit secure channel after connection
    // on the standard FTP port 21.
    Set ComAuthTls Of hoFtp To True

    // The Ssl property is for establishing an implicit SSL connection
    // on port 990.  Because this example uses explicit SSL, it 
    // should remain False.
    Set ComSsl Of hoFtp To False

    // Create an instance of a certificate store object, load a .p12 file,
    // locate the certificate we need, and use it for signing.
    // (a P12/PFX file may contain more than one certificate.)
    Get Create (RefClass(cComChilkatCertStore)) To hoCertStore
    If (Not(IsComObjectCreated(hoCertStore))) Begin
        Send CreateComObject of hoCertStore
    End
    // The 1st argument is the filename, the 2nd arg is the 
    // .p12 file's password.  (OpenSSL will prompty you to set a password
    // when converting the .crt and .key into a .p12).
    Get ComLoadPfxFile Of hoCertStore "test.p12" "secret" To iSuccess
    If (iSuccess <> True) Begin
        Get ComLastErrorText Of hoCertStore To sTemp1
        Showln sTemp1
        Procedure_Return
    End

    Get ComFindCertBySubjectCN Of hoCertStore "Your cert's common name" To vCert
    If (IsComObject(vCert)) Begin
        Get Create (RefClass(cComChilkatCert)) To hoCert
        Set pvComObject Of hoCert To vCert
    End
    Get ComLastMethodSuccess Of hoCertStore To bTemp1
    If (bTemp1 = False) Begin
        Get ComLastErrorText Of hoCertStore To sTemp1
        Showln sTemp1
        Procedure_Return
    End

    Get ComSetSslClientCert Of hoFtp vCert To iSuccess

    Send Destroy of hoCert

    // Connect and login to the FTP server.
    Get ComConnect Of hoFtp To iSuccess
    If (iSuccess <> True) Begin
        Get ComLastErrorText Of hoFtp To sTemp1
        Showln sTemp1
        Procedure_Return
    End
    Else Begin
        // LastErrorText contains information even when
        // successful. This allows you to visually verify
        // that the secure connection actually occurred.
        Get ComLastErrorText Of hoFtp To sTemp1
        Showln sTemp1
    End

    Showln "Secure FTP Channel Established!"
    Get ComLastErrorText Of hoFtp To sTemp1
    Showln sTemp1

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

    // ...
    // ...

    Get ComDisconnect Of hoFtp To iSuccess


End_Procedure