SQL Server

HTTP TLS Mutual Authentication (Client-Side Certificate)

See more HTTP Examples

This example demonstrates what to do when a TLS connection requires a client-side certificate, also known as "two-way authentication" or "mutual authentication". The Chilkat API provides a few standard methods for setting the client-side certificate:

• SetSslClientCert
• SetSslClientPem
• SetSslClientPfx

These methods are present in any Chilkat class that has SSL/TLS functionality. When the SSL client cert is set via one of these methods, it tells the API to use it for two-way (i.e. mutual) authentication. In all possible tasks, whether it is a POST, GET, PUT, an Amazon S3 method, etc., the only thing required for implementing the two-way authentication is to make a successful call to one of the above SetSsl* methods.

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 assumes the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

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

    -- Set the certificate to be used for mutual TLS authentication
    -- (i.e. sets the client-side certificate for two-way TLS authentication)
    EXEC sp_OAMethod @http, 'SetSslClientCertPfx', @success OUT, '/home/bob/pfxFiles/myClientSideCertWithPrivateKey.pfx', 'pfxPassword'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        RETURN
      END

    -- Note: The certificate used for the client-side of TLS mutual authentication
    -- must have the associated private key available. (PFX files typically store both
    -- the certificate and associated private key.)

    -- At this point, the HTTP object is setup with the client-side cert, and any SSL/TLS
    -- connection will automatically use it if the server demands a client-side cert

    EXEC @hr = sp_OADestroy @http


END
GO