Simple signing of PDFs in node.

• node-signpdf
  • Purpose
  • Usage
    • Signing
    • Verifying
  • Notes
  • Signing PDF in simple steps
    • Generate a PDF
    • Append a signature placeholder
    • Generate and apply signature
  • Verifying PDF signature
  • Dependencies
  • Credits
  • Contributing

The purpose of this package is not as much to be used as a dependendency, although it could. The main purpose is to demonstrate the way signing can be achieved in a piece of readable code as it can take a lot of hours to figure out.

Simply said this could be used in two steps. install and sign.

Install with npm i -S node-signpdf node-forge.

Call .sign()

import signer from 'node-signpdf';

const signedPdf = signer.sign(
  fs.readFileSync(PATH_TO_PDF_FILE)
  fs.readFileSync(PATH_TO_P12_CERTIFICATE),
);

In practice we expect that most people will just read through the code we've written in the testing part of this package and figure it out themselves. If that's your case, you should read the [Signing PDF in simple steps] section.

To verify a signed pdf call .verify().

import signer from 'node-signpdf';
...

const signedPdfBuffer = signer.sign(pdfBuffer, p12Buffer);
const {verified} = signer.verify(signedPdfBuffer);

• The process of signing a document is described in the Digital Signatures in PDF document. As Adobe's files are deprecated, here is the standard as defined by ETSI.
• This lib:
  • requires the signature placeholder to already be in the document;
  • requires the Contents descriptor in the Sig be placed after the ByteRange one;
  • takes Buffers of the PDF and a P12 certificate to use when signing;
  • does not cover multiple signatures, incremental updates, etc. Only the basic scenario of signing a freshly created PDF. We actually only worked with documents created with PDFKit;
• Feel free to copy and paste any part of this code. See its defined Purpose.

See the unit-testing code. PDFKit is used there for generating the document. This also allows easy addition of the signature placeholder.

What's needed is a Sig element and a Widget that is also linked in a Form. The form needs to be referenced in the root descriptor of the PDF as well. A (hopefully) readable sample is available in the helpers. Note the Contents descriptor of the Sig where zeros are placed that will later be replaced with the actual signature.

Note: Signing in detached mode makes the signature length independent of the PDF's content length, but it may still vary between different signing certificates. So every time you sign using the same P12 you will get the same length of the output signature, no matter the length of the signed content. It is safe to find out the actual signature length your certificate produces and use it to properly configure the placeholder length.

That's where node-signpdf kicks in. Given a PDF and a P12 certificate a signature is generated in detached mode and is replaced in the placeholder. This is best demonstrated in the tests.

The signed PDF file has the public certificate embeded in it, so all we need to verify a PDF file is the file itself.

node-forge is used for working with signatures.

PDFKit is used in the tests for generating a PDF with a signature placeholder.

• The whole signing flow is a rework of what's already in pdfsign.js so thanks go to @tbocek
• node-forge is an awesome package written in pure JavaScript and supports signing in detached mode. Many thanks to all the guys who wrote and maintain it.
• Thanks to the guys of PDFKit as well. They've made PDF generation incredibly easy.
• This incredible Stack Overflow answer for describing the whole process of verifying PKCS7 signatures.