JavaScript

Create an Opaque Signature with a Separate Private Key

Demonstrates the Chilkat Mime.ConvertToSignedPk method, which creates an opaque signature using a signer certificate and its separately supplied private key. The first argument is the Cert and the second is the PrivateKey.

Note: The file paths are relative to the application's current working directory. Absolute paths may also be used. Supply the paths appropriate to your own environment.

Background: The separate-key form of ConvertToSigned, for when the certificate and private key are not bundled together. It produces the same opaque CMS signed-data result; only the source of the key material differs.

Note

This example is intended for running within a Chilkat.Js embedded JavaScript engine. All Chilkat JavaScript examples require Chilkat v11.4.0 or greater.

JavaScript

var success = false;

var mime = new CkMime();
success = mime.SetBodyFromPlainText("This message will be signed.");
if (success == false) {
    console.log(mime.LastErrorText);
    return;
}

//  Load the certificate and its private key separately.
var cert = new CkCert();
success = cert.LoadFromFile("qa_data/signer.cer");
if (success == false) {
    console.log(cert.LastErrorText);
    return;
}

var privKey = new CkPrivateKey();
success = privKey.LoadPemFile("qa_data/signer_privkey.pem");
if (success == false) {
    console.log(privKey.LastErrorText);
    return;
}

//  Create an opaque signature when the certificate and private key are supplied separately.  The
//  1st argument is the signer certificate and the 2nd is its private key.
success = mime.ConvertToSignedPk(cert,privKey);
if (success == false) {
    console.log(mime.LastErrorText);
    return;
}

success = mime.SaveMime("qa_output/signed_opaque.eml");
if (success == false) {
    console.log(mime.LastErrorText);
    return;
}

console.log("Message converted to an opaque signed message.");