Tcl

Sign PDF in the Cloud using AWS KMS

See more Signing in the Cloud Examples

Demonstrates how to sign a PDF using the AWS Key Management Service. The signing of the hash happens in the Cloud on AWS KMS. Everything else involving the updating the PDF to add the signature happens locally within Chilkat.

Note: This example requires Chilkat v9.5.0.96 or greater.

Tcl

load ./chilkat.dll

set success 0

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

set pdf [new_CkPdf]

# Load a PDF to be signed.
set success [CkPdf_LoadFile $pdf "qa_data/pdf/helloWorld.pdf"]
if {$success == 0} then {
    puts [CkPdf_lastErrorText $pdf]
    delete_CkPdf $pdf
    exit
}

# Options for signing are specified in JSON.
set json [new_CkJsonObject]

# Optionally create an LTV-enabled signature
CkJsonObject_UpdateBool $json "ltvOcsp" 1

# Define the appearance of the signature.
CkJsonObject_UpdateInt $json "page" 1
CkJsonObject_UpdateString $json "appearance.y" "top"
CkJsonObject_UpdateString $json "appearance.x" "left"
CkJsonObject_UpdateString $json "appearance.fontScale" "10.0"
CkJsonObject_UpdateString $json "appearance.text[0]" "Digitally signed by: cert_cn"
CkJsonObject_UpdateString $json "appearance.text[1]" "current_dt"
CkJsonObject_UpdateString $json "appearance.text[2]" "This is an LTV-enabled signature."

# Load the certificate used for signing.  The certificate's private key is stored in AWS KMS
# However, we still need the certificate locally (without private key).
set cert [new_CkCert]

set success [CkCert_LoadFromFile $cert "qa_data/certs/myCert.cer"]
if {$success == 0} then {
    puts [CkCert_lastErrorText $cert]
    delete_CkPdf $pdf
    delete_CkJsonObject $json
    delete_CkCert $cert
    exit
}

# Here's a screenshot of our private key AWS KMS:
# (image:https://example-code.com/images/aws_kms.jpg/endImage)

# To sign using AWS KMS, 
# add the following lines of code to specify your AWS authentication credentials,
# and the ID of the KMS private key.
set jsonAwsKms [new_CkJsonObject]

# Set the "service" equal to "aws_kms" to tell Chilkat to use AWS KMS for signing.
CkJsonObject_UpdateString $jsonAwsKms "service" "aws_kms"
CkJsonObject_UpdateString $jsonAwsKms "access_key" "ACCESS_KEY"
CkJsonObject_UpdateString $jsonAwsKms "secret_key" "SECRET_KEY"
# Make sure to specify the correct region for your case.
CkJsonObject_UpdateString $jsonAwsKms "region" "us-west-2"
# In the above screenshot, our key ID is "187012e8-008f-4fc7-b100-5efe6146dff2".  You will use your key ID.
CkJsonObject_UpdateString $jsonAwsKms "key_id" "187012e8-008f-4fc7-b100-5efe6146dff2"

set success [CkCert_SetCloudSigner $cert $jsonAwsKms]

# Tell the pdf object to use the certificate for signing (and for AWS KMS to do the actual signing of the hash).
set success [CkPdf_SetSigningCert $pdf $cert]
if {$success == 0} then {
    puts [CkPdf_lastErrorText $pdf]
    delete_CkPdf $pdf
    delete_CkJsonObject $json
    delete_CkCert $cert
    delete_CkJsonObject $jsonAwsKms
    exit
}

# Chilkat will build the signed PDF locally, but will (internally) use AWS KMS
# to do the RSA (or EC) sign hash operation.
set success [CkPdf_SignPdf $pdf $json "qa_output/hello_ltv_signed.pdf"]
if {$success == 0} then {
    puts [CkPdf_lastErrorText $pdf]
    delete_CkPdf $pdf
    delete_CkJsonObject $json
    delete_CkCert $cert
    delete_CkJsonObject $jsonAwsKms
    exit
}

puts "PDF Cloud Signing using AWS KMS Successful."

delete_CkPdf $pdf
delete_CkJsonObject $json
delete_CkCert $cert
delete_CkJsonObject $jsonAwsKms