(SQL Server) Create CAdES Signature (.p7s) Compliant with ICP-Brazil Digital Signature Standard PA AD RB v2.2

See more CAdES Examples

Demonstrates how to create a CMS signature w/ policy ID that is compliant with the ICP-Brazil Digital Signature Standard PA AD RB v2.2

For more information, see https://validar.iti.gov.br/

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

    -- ------------------------------------------------------------------------------------------------------
    -- Note: This example creates a CMS signature (.p7s) that contains the PDF.
    -- It is different than signing a PDF.  To sign a PDF where the resulting PDF contains the CMS signature,
    -- see this example:  Sign PDF for ICP-Brasil
    -- ------------------------------------------------------------------------------------------------------

    DECLARE @crypt int
    -- Use "Chilkat_9_5_0.Crypt2" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Crypt2', @crypt OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    DECLARE @cert int
    -- Use "Chilkat_9_5_0.Cert" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Cert', @cert OUT

    DECLARE @success int
    EXEC sp_OAMethod @cert, 'LoadPfxFile', @success OUT, 'mySigningCert.pfx', 'pfxPassword'
    IF @success <> 1
      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

    -- Create JSON to indicate which signing attributes to include.
    DECLARE @attrs int
    -- Use "Chilkat_9_5_0.JsonObject" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @attrs OUT

    EXEC sp_OAMethod @attrs, 'UpdateBool', @success OUT, 'contentType', 1
    EXEC sp_OAMethod @attrs, 'UpdateBool', @success OUT, 'signingTime', 1
    EXEC sp_OAMethod @attrs, 'UpdateBool', @success OUT, 'messageDigest', 1
    EXEC sp_OAMethod @attrs, 'UpdateBool', @success OUT, 'signingCertificateV2', 1

    EXEC sp_OAMethod @attrs, 'UpdateString', @success OUT, 'policyId.hashAlg', 'SHA256'

    -- Listed here are the currently existing profiles. (Chilkat will add additional ICP Brasil policy profiles in future versions as new ones are created.)
    -- See https://www.gov.br/iti/pt-br/assuntos/repositorio/artefatos-de-assinatura-digital for more information.
    -- 
    -- PA_AD_RA --> 2.16.76.1.7.1.5.1
    -- PA_AD_RA_v1_1 --> 2.16.76.1.7.1.5.1.1
    -- PA_AD_RA_v1_2 --> 2.16.76.1.7.1.5.1.2
    -- PA_AD_RA_v2_0 --> 2.16.76.1.7.1.5.2
    -- PA_AD_RA_v2_1 --> 2.16.76.1.7.1.5.2.1
    -- PA_AD_RA_v2_2 --> 2.16.76.1.7.1.5.2.2
    -- PA_AD_RA_v2_3 --> 2.16.76.1.7.1.5.2.3
    -- PA_AD_RA_v2_4 --> 2.16.76.1.7.1.5.2.4
    -- PA_AD_RB --> 2.16.76.1.7.1.1.1
    -- PA_AD_RB_v1_1 --> 2.16.76.1.7.1.1.1.1
    -- PA_AD_RB_v2_0 --> 2.16.76.1.7.1.1.2
    -- PA_AD_RB_v2_1 --> 2.16.76.1.7.1.1.2.1
    -- PA_AD_RB_v2_2 --> 2.16.76.1.7.1.1.2.2
    -- PA_AD_RB_v2_3 --> 2.16.76.1.7.1.1.2.3
    -- PA_AD_RC --> 2.16.76.1.7.1.4.1
    -- PA_AD_RC_v1_1 --> 2.16.76.1.7.1.4.1.1
    -- PA_AD_RC_v2_0 --> 2.16.76.1.7.1.4.2
    -- PA_AD_RC_v2_1 --> 2.16.76.1.7.1.4.2.1
    -- PA_AD_RC_v2_2 --> 2.16.76.1.7.1.4.2.2
    -- PA_AD_RC_v2_3 --> 2.16.76.1.7.1.4.2.3
    -- PA_AD_RT --> 2.16.76.1.7.1.2.1
    -- PA_AD_RT_v1_1 --> 2.16.76.1.7.1.2.1.1
    -- PA_AD_RT_v2_0 --> 2.16.76.1.7.1.2.2
    -- PA_AD_RT_v2_1 --> 2.16.76.1.7.1.2.2.1
    -- PA_AD_RT_v2_2 --> 2.16.76.1.7.1.2.2.2
    -- PA_AD_RT_v2_3 --> 2.16.76.1.7.1.2.2.3
    -- PA_AD_RV --> 2.16.76.1.7.1.3.1
    -- PA_AD_RV_v1_1 --> 2.16.76.1.7.1.3.1.1
    -- PA_AD_RV_v2_0 --> 2.16.76.1.7.1.3.2
    -- PA_AD_RV_v2_1 --> 2.16.76.1.7.1.3.2.1
    -- PA_AD_RV_v2_2 --> 2.16.76.1.7.1.3.2.2
    -- PA_AD_RV_v2_3 --> 2.16.76.1.7.1.3.2.3

    -- Set the policy OID and the profile name
    -- Typically you should use the latest version.
    EXEC sp_OAMethod @attrs, 'UpdateString', @success OUT, 'policyId.id', '2.16.76.1.7.1.1.2.3'
    EXEC sp_OAMethod @attrs, 'UpdateString', @success OUT, 'policyId.profile', 'PA_AD_RB_v2_3'

    -- If you wish to use another, such as v2.2
    EXEC sp_OAMethod @attrs, 'UpdateString', @success OUT, 'policyId.id', '2.16.76.1.7.1.1.2.2'
    EXEC sp_OAMethod @attrs, 'UpdateString', @success OUT, 'policyId.profile', 'PA_AD_RB_v2_2'

    EXEC sp_OAMethod @attrs, 'Emit', @sTmp0 OUT
    EXEC sp_OASetProperty @crypt, 'SigningAttributes', @sTmp0

    -- The input file can be any type of file.
    DECLARE @inFile nvarchar(4000)
    SELECT @inFile = 'toBeSigned.pdf'
    DECLARE @outFile nvarchar(4000)
    SELECT @outFile = 'signed.pdf.p7s'

    EXEC sp_OAMethod @crypt, 'CreateP7M', @success OUT, @inFile, @outFile
    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 @attrs
        RETURN
      END


    PRINT 'Success.'

    EXEC @hr = sp_OADestroy @crypt
    EXEC @hr = sp_OADestroy @cert
    EXEC @hr = sp_OADestroy @attrs


END
GO