Overview
DocuTrust applies cryptographic digital signatures to completed documents using X.509 certificates. Signatures conform to the PAdES (PDF Advanced Electronic Signatures) standard and include RFC 3161 timestamps from a Time Stamping Authority (TSA) to prove the document existed at a specific point in time.Get Current Certificate
Retrieve details about the currently configured signing certificate.Generate Self-Signed Certificate
Generate a new self-signed X.509 certificate for document signing. This replaces any existing certificate.Import Certificate
Import an existing PKCS#12 (.p12 or .pfx) certificate file. This is useful when you have a certificate issued by a trusted Certificate Authority.TSA Timestamping
All digital signatures include an RFC 3161 timestamp from a Time Stamping Authority. This provides cryptographic proof that the signature existed at a specific time, independent of the signer’s local clock.Timestamp Configuration
DocuTrust uses FreeTSA as the primary timestamping authority with an automatic fallback mechanism:
The TSA timestamp is embedded directly into the PDF signature dictionary, making it verifiable by any PAdES-compliant reader (Adobe Acrobat, Foxit, etc.).
Signature Structure
Each signed document contains:PAdES Compliance
DocuTrust signatures are PAdES-B (Basic) compliant:Verification
Signed documents can be verified using:- Adobe Acrobat Reader — Opens the Signatures panel automatically
- Foxit PDF Reader — Displays signature validity in the toolbar
- Any PAdES-compliant validator — The PKCS#7 structure is standard-compliant
Self-signed certificates will show as “unknown” trust in PDF readers. For full trust chain validation, import a certificate issued by a publicly trusted Certificate Authority.