SQL Server

CoSign PKCS7/CMS Signed Data

See more Digital Signatures Examples

Demonstrates how to add a 2nd signature to a CMS SignedData. This is to add an additional signature, SignerInfo and certificate(s) to an existing CMS signed data.

In this example, we cosign an existing pdf.p7s

Note: The CoSign method is added in Chilkat v9.5.0.89.

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 @crypt int
    EXEC @hr = sp_OACreate 'Chilkat.Crypt2', @crypt OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

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

    -- If loading from a smart card, set the smartcard PIN.
    EXEC sp_OASetProperty @cert, 'SmartCardPin', '0000'

    -- Load a certificate in some way, such as from a smart card.
    -- Chilkat provides other methods to load from a .pfx, .pem, or from the Windows certificate stores..
    EXEC sp_OAMethod @cert, 'LoadFromSmartcard', @success OUT, ''
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @cert, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @crypt
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END

    EXEC sp_OAMethod @crypt, 'SetSigningCert', @success OUT, @cert
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @crypt, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @crypt
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END

    -- Load the file to be co-signed.
    -- NOTE:  This is to cosign a PDF file contained within a CMS (PKCS7) message.
    -- (In other words, the PDF is contained within the CMS SignedData, rather than the other way around
    -- where a CMS signature is contained within a PDF.  Use Chilkat's PDF class to sign a PDF, which is
    -- to embed a CMS signature within the PDF.)
    DECLARE @bd int
    EXEC @hr = sp_OACreate 'Chilkat.BinData', @bd OUT

    EXEC sp_OAMethod @bd, 'LoadFile', @success OUT, 'qa_data/p7s/cosign/sample.pdf.p7s'
    IF @success = 0
      BEGIN

        PRINT 'Failed to load pdf.p7s input file.'
        EXEC @hr = sp_OADestroy @crypt
        EXEC @hr = sp_OADestroy @cert
        EXEC @hr = sp_OADestroy @bd
        RETURN
      END

    -- bd2 will contain the co-signed result.
    DECLARE @bd2 int
    EXEC @hr = sp_OACreate 'Chilkat.BinData', @bd2 OUT

    EXEC sp_OAMethod @crypt, 'CoSign', @success OUT, @bd, @cert, @bd2
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @crypt, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @crypt
        EXEC @hr = sp_OADestroy @cert
        EXEC @hr = sp_OADestroy @bd
        EXEC @hr = sp_OADestroy @bd2
        RETURN
      END

    EXEC sp_OAMethod @bd, 'WriteFile', @success OUT, 'qa_output/cosigned.pdf.p7s'
    IF @success = 0
      BEGIN

        PRINT 'Failed to save pdf.p7s output file.'
        EXEC @hr = sp_OADestroy @crypt
        EXEC @hr = sp_OADestroy @cert
        EXEC @hr = sp_OADestroy @bd
        EXEC @hr = sp_OADestroy @bd2
        RETURN
      END


    PRINT 'Success!'

    EXEC @hr = sp_OADestroy @crypt
    EXEC @hr = sp_OADestroy @cert
    EXEC @hr = sp_OADestroy @bd
    EXEC @hr = sp_OADestroy @bd2


END
GO