Chilkat Examples

ChilkatHOME.NET Core C#Android™AutoItCC#C++Chilkat2-PythonCkPythonClassic ASPDataFlexDelphi ActiveXDelphi DLLGoJavaLianjaMono C#Node.jsObjective-CPHP ActiveXPHP ExtensionPerlPowerBuilderPowerShellPureBasicRubySQL ServerSwift 2Swift 3,4,5...TclUnicode CUnicode C++VB.NETVBScriptVisual Basic 6.0Visual FoxProXojo Plugin

SQL Server Examples

Web API Categories

ASN.1
AWS KMS
AWS Misc
Amazon EC2
Amazon Glacier
Amazon S3
Amazon S3 (new)
Amazon SES
Amazon SNS
Amazon SQS
Async
Azure Cloud Storage
Azure Key Vault
Azure Service Bus
Azure Table Service
Base64
Bounced Email
Box
CAdES
CSR
CSV
Certificates
Code Signing
Compression
DKIM / DomainKey
DNS
DSA
Diffie-Hellman
Digital Signatures
Dropbox
Dynamics CRM
EBICS
ECC
Ed25519
Email Object
Encryption
FTP
FileAccess
Firebase
GMail REST API
GMail SMTP/IMAP/POP
Geolocation
Google APIs
Google Calendar
Google Cloud SQL
Google Cloud Storage
Google Drive
Google Photos
Google Sheets
Google Tasks
Gzip
HTML-to-XML/Text
HTTP

HTTP Misc
IMAP
JSON
JSON Web Encryption (JWE)
JSON Web Signatures (JWS)
JSON Web Token (JWT)
Java KeyStore (JKS)
MHT / HTML Email
MIME
MS Storage Providers
Microsoft Graph
Misc
NTLM
OAuth1
OAuth2
OIDC
Office365
OneDrive
OpenSSL
Outlook
Outlook Calendar
Outlook Contact
PDF Signatures
PEM
PFX/P12
PKCS11
POP3
PRNG
REST
REST Misc
RSA
SCP
SCard
SFTP
SMTP
SSH
SSH Key
SSH Tunnel
ScMinidriver
SharePoint
SharePoint Online
Signing in the Cloud
Socket/SSL/TLS
Spider
Stream
Tar Archive
ULID/UUID
Upload
WebSocket
XAdES
XML
XML Digital Signatures
XMP
Zip
curl
uncategorized

 

 

 

(SQL Server) 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

// 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
    DECLARE @sTmp0 nvarchar(4000)
    -- 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_9_5_0.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', '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_9_5_0.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).
    DECLARE @success int
    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 @cert int
    EXEC sp_OAMethod @certStore, 'FindCertBySubjectCN', @cert OUT, 'Your cert''s common name'
    EXEC sp_OAGetProperty @certStore, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 = 0
      BEGIN
        EXEC sp_OAGetProperty @certStore, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        EXEC @hr = sp_OADestroy @certStore
        RETURN
      END

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

    EXEC @hr = sp_OADestroy @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
        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


END
GO

 

© 2000-2024 Chilkat Software, Inc. All Rights Reserved.