Add a Detached Signature (Separate Key, Header Control)

See more MIME Examples

Demonstrates the Chilkat Mime.AddDetachedSignaturePk2 method, which creates a detached signature with a separately supplied certificate and private key, and a third argument controlling transfer of the existing message header fields to the new outer entity.

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.

NODEJS_PRELUDE

function chilkatExample() {

    var success = false;

    var mime = new chilkat.Mime();
    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 chilkat.Cert();
    success = cert.LoadFromFile("qa_data/signer.cer");
    if (success == false) {
        console.log(cert.LastErrorText);
        return;
    }

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

    //  Create a detached signature with separately supplied cert and private key, where the 3rd
    //  argument controls whether the existing message header fields are transferred to the new outer
    //  multipart/signed entity.
    var transferHeaderFields = true;
    success = mime.AddDetachedSignaturePk2(cert,privKey,transferHeaderFields);
    if (success == false) {
        console.log(mime.LastErrorText);
        return;
    }

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

    console.log("Detached signature added (headers transferred).");

}

chilkatExample();