SQL Server

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

See more FTP Examples

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.

SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

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

    DECLARE @ftp int
    EXEC @hr = sp_OACreate 'Chilkat.Ftp2', @ftp OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    EXEC sp_OASetProperty @ftp, 'Hostname', 'ftp.example.com'
    EXEC sp_OASetProperty @ftp, 'Port', 21
    EXEC sp_OASetProperty @ftp, 'Username', 'testLogin'
    EXEC sp_OASetProperty @ftp, 'Password', 'testPassword'

    -- This example will use explict TLS/SSL.
    -- Establish an explicit secure channel after connection
    -- on the standard FTP port 21.
    EXEC sp_OASetProperty @ftp, 'AuthTls', 1

    -- The Ssl property is for establishing an implicit SSL connection
    -- on port 990.  Because this example uses explicit SSL, it 
    -- should remain 0.
    EXEC sp_OASetProperty @ftp, 'Ssl', 0

    -- 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.)
    DECLARE @certStore int
    EXEC @hr = sp_OACreate 'Chilkat.CertStore', @certStore OUT

    -- 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).
    EXEC sp_OAMethod @certStore, 'LoadPfxFile', @success OUT, 'test.p12', 'secret'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @certStore, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        EXEC @hr = sp_OADestroy @certStore
        RETURN
      END

    DECLARE @jsonCN int
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jsonCN OUT

    EXEC sp_OAMethod @jsonCN, 'UpdateString', @success OUT, 'CN', 'cert common name'

    DECLARE @cert int
    EXEC @hr = sp_OACreate 'Chilkat.Cert', @cert OUT

    EXEC sp_OAMethod @certStore, 'FindCert', @success OUT, @jsonCN, @cert
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @certStore, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        EXEC @hr = sp_OADestroy @certStore
        EXEC @hr = sp_OADestroy @jsonCN
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END

    EXEC sp_OAMethod @ftp, 'SetSslClientCert', @success OUT, @cert

    -- Connect and login to the FTP server.
    EXEC sp_OAMethod @ftp, 'Connect', @success OUT
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        EXEC @hr = sp_OADestroy @certStore
        EXEC @hr = sp_OADestroy @jsonCN
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END
    ELSE
      BEGIN
        -- LastErrorText contains information even when
        -- successful. This allows you to visually verify
        -- that the secure connection actually occurred.
        EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
      END


    PRINT 'Secure FTP Channel Established!'
    EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
    PRINT @sTmp0

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

    -- ...
    -- ...

    EXEC sp_OAMethod @ftp, 'Disconnect', @success OUT

    EXEC @hr = sp_OADestroy @ftp
    EXEC @hr = sp_OADestroy @certStore
    EXEC @hr = sp_OADestroy @jsonCN
    EXEC @hr = sp_OADestroy @cert


END
GO