React Native Requires Chilkat v11.5.0+

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. React Native

import { Cert, Crypt2, JsonObject } from '@chilkat/react-native'

async function chilkatExample() {
  // 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).
  const cert = new Cert();
  try {
    cert.loadFromFile('qa_data/certs/myCert.cer');
  } catch {
    console.log(cert.lastErrorText);
    return;
  }

  // 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.
  const jsonArss = new JsonObject();

  // 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');

  await cert.setCloudSignerAsync(jsonArss);

  const crypt = new Crypt2();

  try {
    crypt.setSigningCert(cert);
  } catch {
    console.log(crypt.lastErrorText);
    return;
  }

  // The CadesEnabled property applies to all methods that create PKCS7 signatures. 
  // To create a CAdES-BES signature, set this property equal to true.
  crypt.cadesEnabled = true;

  crypt.hashAlgorithm = 'sha256';

  const signedAttrs = new JsonObject();
  signedAttrs.updateInt('contentType', 1);
  signedAttrs.updateInt('signingTime', 1);
  signedAttrs.updateInt('messageDigest', 1);
  signedAttrs.updateInt('signingCertificateV2', 1);
  crypt.signingAttributes = signedAttrs.emit();

  // You can sign any type of file..
  const inputXmlPath = 'qa_data/e-Invoice.xml';
  const 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.
  try {
    await crypt.createP7MAsync(inputXmlPath, outputP7mPath);
  } catch {
    console.log(crypt.lastErrorText);
    return;
  }

  console.log('Success.');
}