Perl

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. Perl

use chilkat();

$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).
$cert = chilkat::CkCert->new();
$success = $cert->LoadFromFile("qa_data/certs/myCert.cer");
if ($success == 0) {
    print $cert->lastErrorText() . "\r\n";
    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.
$jsonArss = chilkat::CkJsonObject->new();

# Set the "service" equal to "ARSS" to tell Chilkat to use ARSS for signing.
$jsonArss->UpdateString("service","ARSS");
# Specify the certificate ID, such as "AS0"
# This certificate should match the certificate loaded in the above code.
$jsonArss->UpdateString("certID","YOUR_ARSS_CERT_ID");
$jsonArss->UpdateString("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.
$jsonArss->UpdateString("typeOtpAuth","demoprod");

$jsonArss->UpdateString("user","YOUR_ARSS_USERNAME");
$jsonArss->UpdateString("userPWD","YOUR_ARSS_PASSWORD");

# The "endpoint" can be specified starting in Chilkat v11.5.0
$jsonArss->UpdateString("endpoint","https://app1.firma-remota.it/ArubaSignerService/webresources/signerservice");

$success = $cert->SetCloudSigner($jsonArss);

$crypt = chilkat::CkCrypt2->new();

$success = $crypt->SetSigningCert($cert);
if ($success == 0) {
    print $crypt->lastErrorText() . "\r\n";
    exit;
}

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

$crypt->put_HashAlgorithm("sha256");

$signedAttrs = chilkat::CkJsonObject->new();
$signedAttrs->UpdateInt("contentType",1);
$signedAttrs->UpdateInt("signingTime",1);
$signedAttrs->UpdateInt("messageDigest",1);
$signedAttrs->UpdateInt("signingCertificateV2",1);
$crypt->put_SigningAttributes($signedAttrs->emit());

# You can sign any type of file..
$inputXmlPath = "qa_data/e-Invoice.xml";
$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.
$success = $crypt->CreateP7M($inputXmlPath,$outputP7mPath);
if ($success == 0) {
    print $crypt->lastErrorText() . "\r\n";
    exit;
}

print "Success." . "\r\n";