(SQL Server) Load Default Certificate from Smart Card or Token

See more Certificates Examples

Chilkat contains internal logic to examine a connected smart card or USB token, and will make decisions based on make/model to successfully interact with the hardware. When faced with a new smartcard or token, the best starting point is to call LoadFromSmartcard with an empty string argument to see what Chilkat discovers.

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
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @sTmp1 nvarchar(4000)
    DECLARE @cert int
    -- Use "Chilkat_9_5_0.Cert" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Cert', @cert OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- If you know the smart card PIN, it's good to set it prior to loading from the smartcard/USB token.
    EXEC sp_OASetProperty @cert, 'SmartCardPin', '12345678'

    -- To let Chilkat discover what smartcard or token is connected, pass an empty string to LoadFromSmartcard.
    -- When testing in this way, it's best to have only a single smartcard or token connected to the system.
    DECLARE @success int
    EXEC sp_OAMethod @cert, 'LoadFromSmartcard', @success OUT, ''
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @cert, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0

        PRINT 'Certificate not loaded.'
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END

    -- The LastErrorText property on all Chilkat objects will contain 
    -- information even when the method call is successful.
    -- You can examine the LastErrorText to see what Chilkat found and
    -- what decisions were made.
    -- 
    -- For example, if a certificate was successfully loaded via LoadFromSmartcard,
    -- but then signing failed, such as w/ Pdf, XmlDSig, CAdES, etc.,
    -- then we would want to examine the LastErrorText from the call to
    -- LoadFromSmartcard to get detailed information about the card.
    EXEC sp_OAGetProperty @cert, 'LastErrorText', @sTmp0 OUT
    PRINT @sTmp0


    EXEC sp_OAGetProperty @cert, 'SubjectDN', @sTmp0 OUT

    EXEC sp_OAGetProperty @cert, 'SerialNumber', @sTmp1 OUT
    PRINT 'Found: ' + @sTmp0 + ' serial=' + @sTmp1

    EXEC @hr = sp_OADestroy @cert


END
GO