Cookbook

The cookbook is a set of copy-paste Rust recipes. Each one is a self-contained snippet you drop straight into your own project — use mudrit::prelude::*;, point it at your DSC and input PDF, handle the Result — not a program you have to check out and run. The recipes are grouped by category below.

How the recipes are written

Every recipe imports the facade prelude and uses realistic variable names and placeholder paths:

use mudrit::prelude::*;

let signer = PfxSigner::from_file("signer.pfx", "password")?;   // your DSC — file / token / store
let pdf    = std::fs::read("input.pdf")?;                       // the document you want to sign

let cfg = SignConfig::builder()
    .place("L", [350, 60, 560, 160])?
    .reason("Approved")
    .build();

let signed = sign_pdf(&pdf, &signer, &cfg)?;
std::fs::write("signed.pdf", &signed)?;

Swapping the key source (PfxSigner → Pkcs11Signer → WinStoreSigner → your own Signer) is the only change needed to sign from a token, the Windows store, or a cloud KMS — the SignConfig and the sign_pdf call stay identical. See Signing Backends.

Bundled test fixtures (source bundle)

The example programs in the source bundle read their inputs from a workspace-root samples/ directory and write outputs to temp/. If you have the bundle, these are the fixtures they use; if you don't, they are simply the stand-ins the recipes reference — substitute your own files.

Internal SDK validation

Beyond the per-recipe programs, the source bundle also carries an internal verification harness — a 65-scenario matrix run against every keystore and every algorithm, writing one PDF per scenario into temp/<keystore>/<mechanism>/. That harness is a tool for SDK developers validating the engine, not something integrators run. It is documented, for completeness, in the Advanced page's Internal section.

Browse by category