(SQL Server) Secure FTP with Client Certificate

Chilkat FTP2 provides the ability to use a client certificate with secure FTP (implicit or explicit SSL/TLS). This example demonstrates how to load a certificate from a .pfx and use it as the client-side SSL cert. Note: Client-side certificates are only needed in situations where the server demands one.

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

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    -- This example requires the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @ftp int
    -- Use "Chilkat_9_5_0.Ftp2" for versions of Chilkat < 10.0.0
    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.***.com'
    EXEC sp_OASetProperty @ftp, 'Port', 21
    EXEC sp_OASetProperty @ftp, 'Username', 'test'
    EXEC sp_OASetProperty @ftp, 'Password', 'test'

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

    -- Load a certificate from a .pfx
    -- A PFX may contain several certs, including the certificates
    -- in a chain of authority.
    DECLARE @certStore int
    -- Use "Chilkat_9_5_0.CertStore" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.CertStore', @certStore OUT

    DECLARE @password nvarchar(4000)

    SELECT @password = '***'
    -- Load the certs from a PFX into an in-memory certificate store:
    DECLARE @success int
    EXEC sp_OAMethod @certStore, 'LoadPfxFile', @success OUT, 'chilkat.pfx', @password
    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

    -- Find the exact cert we'll use:
    DECLARE @cert int

    EXEC sp_OAMethod @certStore, 'FindCertBySubject', @cert OUT, 'Chilkat Software, Inc.'
    EXEC sp_OAGetProperty @certStore, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 = 0
      BEGIN

        PRINT 'Certificate not found!'
        EXEC @hr = sp_OADestroy @ftp
        EXEC @hr = sp_OADestroy @certStore
        RETURN
      END

    -- Use this certificate for our secure (SSL/TLS) connection:
    EXEC sp_OAMethod @ftp, 'SetSslClientCert', @success OUT, @cert
    EXEC @hr = sp_OADestroy @cert

    -- Connect and login to the FTP server.  The connection is 
    -- made secure because of the AuthTls setting.
    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
        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!'

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


END
GO