๐Ÿ”ฌ Sign PDF documents with X.509 certificates using PAdES standards

โšก 149 views ยท ๐Ÿ”ฌ Document Extraction & Analysis

Description

PDF Digital Signature API with PAdES Compliance

Sign PDF documents with legally-compliant digital signatures using X.509 certificates. Supports multiple PAdES signature levels (B, T, LT, LTA) with optional visible stamps.

What this workflow does

This workflow creates a professional PDF signing service that:

Perfect for contracts, invoices, legal documents, and any PDF requiring digital authentication.

Use Cases

How it Works

Workflow Process

  1. File Upload: Receives PDF, certificate (PFX), and password via webhook
  2. Dependency Check: Automatically installs Java and signing tool if needed
  3. Certificate Processing: Extracts certificate and private key from PFX
  4. Signature Selection: Routes to appropriate signing method based on level
  5. PDF Signing: Signs document using open-pdf-sign tool
  6. Response: Returns signed PDF and cleans up temporary files

Signature Levels Explained

Choose the signature level based on your needs:

BASELINE-B (Basic, 2-3 seconds)

BASELINE-T (Timestamp, 3-5 seconds) - Recommended

BASELINE-LT (Long-Term, 5-10 seconds)

BASELINE-LTA (Archival, 8-12 seconds)

Visible vs Invisible Signatures

Invisible (default):

Visible:

Customization

Change Signature Level

Modify the signLevel parameter in your request:

Customize Visible Signature

Upload a logo and add customization parameters to the signing command nodes:

--hint "Digitally Signed"           # Custom text
--page 2                            # Sign on page 2
--label-signee "Signed by"          # Custom label
--label-timestamp "Date"            # Custom timestamp label
--no-hint                           # Hide hint row
--signature-reason "Contract Approval"  # Reason text

Adjust File Paths

Modify these nodes to change temporary file locations:

Add Authentication

For production use, add authentication before the webhook:

  1. Insert HTTP Request node to validate API key
  2. Add rate limiting
  3. Log signature operations

Technical Details

What Gets Installed

The workflow automatically installs:

Certificate Processing

Uses OpenSSL to extract:

All files use timestamped names to prevent conflicts.

Security Features

Standards Compliance

Implements ETSI EN 319 142 PAdES standards:

FAQ

Q: Where do I get certificates? A: For testing, use free certificates from Codegic. For production, purchase from DigiCert, GlobalSign, or Sectigo.

Q: What PDF sizes are supported? A: Up to 50MB by default. Adjust n8n configuration for larger files.

Q: Can I sign multiple PDFs at once? A: Call the API once per PDF, or modify the workflow to accept multiple files.

Q: Will signatures work in Adobe Reader? A: Yes, if using certificates from trusted CAs. Self-signed certificates will show warnings.

Q: How do I verify signed PDFs? A: Open in Adobe Acrobat Reader and check the signature panel, or use the EU DSS validation tool webapp.

Q: Can I use this commercially? A: Yes, the workflow is free for personal and commercial use.

Support


License: Free for personal and commercial use
Dependencies: OpenJDK 11, OpenSSL, curl, open-pdf-sign v0.3.0 (Apache 2.0)

๐Ÿ”— Nodes Used

HTTP Request, Read Binary File, Webhook, Read/Write Files from Disk

๐Ÿ“ฅ Import

Download workflow.json and import into n8n: Workflow menu โ†’ Import from File

๐Ÿ“– Importing guide ยท ๐Ÿ”‘ Credential setup