Tcl

Include the SigningCertificateV2 Authenticated Attribute in CAdES (CMS) Signature

See more CAdES Examples

Demonstrates how to include the SigningCertificateV2 authenticated attribute in a CMS (.p7m/.p7s) signature. Tcl

load ./chilkat.dll

set success 0

# This example assumes the Chilkat API to have been previously unlocked.
# See Global Unlock Sample for sample code.

set crypt [new_CkCrypt2]

set cert [new_CkCert]

set success [CkCert_LoadPfxFile $cert "qa_data/pfx/cert_test123.pfx" "test123"]
if {$success != 1} then {
    puts [CkCert_lastErrorText $cert]
    delete_CkCrypt2 $crypt
    delete_CkCert $cert
    exit
}

# Tell the crypt component to use this cert.
set success [CkCrypt2_SetSigningCert $crypt $cert]
if {$success != 1} then {
    puts [CkCrypt2_lastErrorText $crypt]
    delete_CkCrypt2 $crypt
    delete_CkCert $cert
    exit
}

# The CadesEnabled property applies to all methods that create PKCS7 signatures. 
# To create a CAdES-BES signature, set this property equal to true. 
CkCrypt2_put_CadesEnabled $crypt 1

CkCrypt2_put_HashAlgorithm $crypt "sha256"

# We can sign any type of file, creating a .p7s as output.
# The .p7s contains the signature and also embeds the data of the file that is signed.
set inFile "qa_data/pdf/sample.pdf"
set p7sFile "qa_output/sample.pdf.p7s"

set jsonSigningAttrs [new_CkJsonObject]

CkJsonObject_UpdateInt $jsonSigningAttrs "contentType" 1
CkJsonObject_UpdateInt $jsonSigningAttrs "signingTime" 1
CkJsonObject_UpdateInt $jsonSigningAttrs "messageDigest" 1

# This is where we specify for the signingCertificateV2 attribute to be included:
CkJsonObject_UpdateInt $jsonSigningAttrs "signingCertificateV2" 1

CkCrypt2_put_SigningAttributes $crypt [CkJsonObject_emit $jsonSigningAttrs]

# By default, all the certs in the chain of authentication are included in the signature.
# If desired, we can choose to only include the signing certificate:
CkCrypt2_put_IncludeCertChain $crypt 0

# Create the CAdES-BES attached signature, which contains the original data.
# Note: Chilkat's function naming is not accurate.  CreateP7M creates a PKCS7 signature where the signed file
# is contained within the signature.  CreateP7S creates a detached PKCS7 signature where the signed file
# is NOT contained within the signature.  We want the data to be contained in the signature, therefore
# we call CreateP7M even though we are naming our output file .p7s.
set success [CkCrypt2_CreateP7M $crypt $inFile $p7sFile]
if {$success == 0} then {
    puts [CkCrypt2_lastErrorText $crypt]
    delete_CkCrypt2 $crypt
    delete_CkCert $cert
    delete_CkJsonObject $jsonSigningAttrs
    exit
}

# Verify the .p7s file and extract the original file from the .p7s. 
set extractedToFilePath "qa_output/sample.pdf"
set success [CkCrypt2_VerifyP7M $crypt $p7sFile $extractedToFilePath]
if {$success == 0} then {
    puts [CkCrypt2_lastErrorText $crypt]
    delete_CkCrypt2 $crypt
    delete_CkCert $cert
    delete_CkJsonObject $jsonSigningAttrs
    exit
}

puts "Success!"

delete_CkCrypt2 $crypt
delete_CkCert $cert
delete_CkJsonObject $jsonSigningAttrs