React Native

Supply a Fallback Certificate for S/MIME Verification

Demonstrates the Chilkat Mime.SetVerifyCert method, which supplies a signer-certificate fallback for subsequent signature verification. The only argument is the Cert.

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: Most signed messages embed the signer's certificate, so Verify can find it automatically. But some signatures omit it to save space, expecting the recipient to already have it. This method provides that certificate as a fallback so verification can proceed — the S/MIME equivalent of already knowing the sender's public key out of band.

Chilkat React Native Downloads

Download Chilkat for React Native

React Native

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

function chilkatExample() {
  const mime = new Mime();
  try {
    mime.loadMimeFile('qa_data/signed.eml');
  } catch {
    console.log(mime.lastErrorText);
    return;
  }

  // Supply a signer-certificate fallback for verification.  This is useful when the signature does
  // not embed the signer certificate and Chilkat cannot otherwise locate it.
  const cert = new Cert();
  try {
    cert.loadFromFile('qa_data/signer.cer');
  } catch {
    console.log(cert.lastErrorText);
    return;
  }

  try {
    mime.setVerifyCert(cert);
  } catch {
    console.log(mime.lastErrorText);
    return;
  }

  // Now verify using the supplied certificate.
  try {
    mime.verify();
  } catch {
    console.log(mime.lastErrorText);
    return;
  }

  console.log('Signature verified using the supplied certificate.');
}