Skip to content

Server Edition

Jump to bottom
Liviu Stoica edited this page May 20, 2026 · 1 revision

Server Edition — Folder Watch with SEAL

The Server Edition adds automated, unattended signing. XignAll monitors a folder and signs every file that appears in it — no user interaction required.

How it works

XignAll watches a root folder (/SEAL/) and its first-level subfolders. When a new file appears:

  1. If not a PDF → converted automatically (same engine as Pipeline tab)
  2. Signed with the configured SEAL profile
  3. Moved to [subfolder]/Signed/
  4. On error → moved to [subfolder]/Failed/ with an entry in the journal
/SEAL/
├── Finance/
│   ├── invoice.docx        ← drop file here
│   ├── Signed/             ← signed PDF output
│   └── Failed/             ← errors
├── HR/
│   ├── Signed/
│   └── Failed/
└── ...

Supported input formats (auto-converted)

.docx · .doc · .odt · .rtf · .txt · .xlsx · .xls · .ods · .csv · .jpg · .jpeg · .png · .bmp · .tiff · .gif · .webp · .pdf

SEAL profile

The SEAL is an organizational electronic seal — a signature applied by the organization (not an individual). In the eIDAS framework this corresponds to an Electronic Seal (eSeal).

Configuration: Server tab → SEAL Settings → select a signer profile configured in the Sign tab (PKCS#12 or PKCS#11).

PIN handling:

  • PIN entered once when starting the watch service
  • Stored encrypted in memory — never written to disk
  • Wrong PIN detection: if PKCS#11 returns an incorrect PIN error, the watch stops immediately to prevent hardware token lockout

Combined workflow (internal signers + SEAL)

You can combine the serial workflow with the folder watch:

  1. Configure internal signers in the Workflow tab
  2. Enable SEAL in Server settings
  3. When a file arrives: internal signers sign first (in order), SEAL is applied last
  4. The SEAL certifies the fully-signed document

Security

  • Path traversal protection: file paths are validated before processing — files cannot escape the watch root
  • Atomic PDF write: signed PDF is written to a temp file first, then renamed — no partial files on crash or power loss
  • Subfolder isolation: each department/subfolder has its own Signed/ and Failed/ — files do not mix

Journal

The Server tab includes a real-time journal showing:

  • Files processed (filename, subfolder, timestamp)
  • Result: signed / failed / skipped
  • Error details for failed files

Journal is also accessible via Telegram bot admin command /log.

Pricing

Server Edition: €49.99/month · €499.99/year · €799 perpetual

→ See all plans

Clone this wiki locally