Tcl

Create CAdES (p7m) Signature using ARSS (Aruba Remote Signing Service)

See more Signing in the Cloud Examples

Demonstrates creating a CAdES (p7m) signature using the Aruba Remote Signing Service. 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.

# Load the certificate used for signing.  The certificate's private key is stored on 
# the Aruba.it server and the signing will happen remotely using the
# ARSS (Aruba Remote Signing Service).
# 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_CkCert $cert
    exit
}

# To sign using the Aruba Remote Signing Service, 
# add the following lines of code to specify your authentication credentials,
# and the ID of the certificate w/ private key on the server to be used.
set jsonArss [new_CkJsonObject]

# Set the "service" equal to "ARSS" to tell Chilkat to use ARSS for signing.
CkJsonObject_UpdateString $jsonArss "service" "ARSS"
# Specify the certificate ID, such as "AS0"
# This certificate should match the certificate loaded in the above code.
CkJsonObject_UpdateString $jsonArss "certID" "YOUR_ARSS_CERT_ID"
CkJsonObject_UpdateString $jsonArss "otpPwd" "YOUR_OTP_PWD"

# Specifies the OTP authentication environment.
# 
# Common values are:
#   "demoprod" - Demo/Test environment
#   "prod"     - Production environment
# 
# This value is sent to the ARSS service and determines how the OTP
# authentication is validated.  The correct value depends on the type
# of Aruba account and environment that has been provisioned.
# 
# If signing fails with an authentication-related error, verify that
# the typeOtpAuth value matches the environment associated with the
# ARSS account credentials being used.
CkJsonObject_UpdateString $jsonArss "typeOtpAuth" "demoprod"

CkJsonObject_UpdateString $jsonArss "user" "YOUR_ARSS_USERNAME"
CkJsonObject_UpdateString $jsonArss "userPWD" "YOUR_ARSS_PASSWORD"

# The "endpoint" can be specified starting in Chilkat v11.5.0
CkJsonObject_UpdateString $jsonArss "endpoint" "https://app1.firma-remota.it/ArubaSignerService/webresources/signerservice"

set success [CkCert_SetCloudSigner $cert $jsonArss]

set crypt [new_CkCrypt2]

set success [CkCrypt2_SetSigningCert $crypt $cert]
if {$success == 0} then {
    puts [CkCrypt2_lastErrorText $crypt]
    delete_CkCert $cert
    delete_CkJsonObject $jsonArss
    delete_CkCrypt2 $crypt
    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"

set signedAttrs [new_CkJsonObject]

CkJsonObject_UpdateInt $signedAttrs "contentType" 1
CkJsonObject_UpdateInt $signedAttrs "signingTime" 1
CkJsonObject_UpdateInt $signedAttrs "messageDigest" 1
CkJsonObject_UpdateInt $signedAttrs "signingCertificateV2" 1
CkCrypt2_put_SigningAttributes $crypt [CkJsonObject_emit $signedAttrs]

# You can sign any type of file..
set inputXmlPath "qa_data/e-Invoice.xml"
set outputP7mPath "qa_output/signed.p7m"

# Create the CAdES-BES attached signature, which contains the original data.
# Chilkat will build the .p7m locally, but will (internally) use ARSS
# to do the RSA signing remotely.
set success [CkCrypt2_CreateP7M $crypt $inputXmlPath $outputP7mPath]
if {$success == 0} then {
    puts [CkCrypt2_lastErrorText $crypt]
    delete_CkCert $cert
    delete_CkJsonObject $jsonArss
    delete_CkCrypt2 $crypt
    delete_CkJsonObject $signedAttrs
    exit
}

puts "Success."

delete_CkCert $cert
delete_CkJsonObject $jsonArss
delete_CkCrypt2 $crypt
delete_CkJsonObject $signedAttrs