Skip to content

Digital ID (PKI Certificates)

A Digital ID (also called a digital certificate or PKI certificate) is the cornerstone of secure, legally binding electronic signatures. This page explains what Digital IDs are, why they matter, and how to configure them in WPsigner.

A Digital ID is a cryptographic certificate that:

  1. Verifies your identity - Proves who signed the document
  2. Seals the document - Creates a tamper-evident container
  3. Establishes trust - Third-party validation of authenticity
  4. Enables long-term validity - Signatures remain valid for years

Think of it as a digital passport or notary stamp for your electronic documents.


Without a Digital ID, your signed PDF is essentially just an image of a signature placed on a document. Anyone could:

  • Modify the document after signing
  • Claim the signature was forged
  • Dispute when the document was signed
  • Question who actually signed

A Digital ID provides cryptographic proof:

Without Digital IDWith Digital ID
Signature is just an imageSignature is cryptographically bound
Document can be modifiedAny modification breaks the seal
No identity verificationIdentity verified by certificate
Easy to disputeLegally defensible
Poor complianceFull regulatory compliance

Digital IDs enable compliance with major e-signature regulations:

RegulationRegionDigital ID Role
ESIGN ActUSAProvides intent attribution
UETAUSA (all states)Establishes signer identity
eIDASEuropean UnionRequired for Advanced/Qualified signatures
ZertESSwitzerlandRequired for qualified signatures
IT ActIndiaRequired for legally valid signatures

In legal disputes, digitally signed documents with valid certificates are:

  • Self-authenticating - No additional witness required
  • Tamper-evident - Any changes are detectable
  • Non-repudiable - Signer cannot deny signing
  • Time-bound - Timestamped for provenance

Certain industries require digital certificates:

IndustryRequirementReason
HealthcareHIPAA compliancePHI protection
FinanceSOX, PCI-DSSFinancial records integrity
GovernmentNIST, FedRAMPSecurity standards
LegalBar association rulesDocument authenticity
PharmaFDA 21 CFR Part 11Regulatory submissions

Created by you, for internal use.

Best For:

  • Internal company documents
  • Testing and development
  • Non-legal agreements
  • Team acknowledgments

Pros:

  • Free to create
  • Instant availability
  • Full control

Cons:

  • Not trusted by default in Adobe Reader
  • Recipients see “Unknown Signer” warning
  • Less credible for external parties

Purchased from a trusted Certificate Authority (CA).

Best For:

  • Client-facing contracts
  • Legal agreements
  • Regulatory filings
  • Any document requiring third-party validation

Pros:

  • Automatically trusted in Adobe Reader
  • CA verifies your identity
  • Higher legal weight
  • Green checkmark in Adobe

Cons:

  • Annual cost ($200-$500/year)
  • Identity verification process
  • Renewal required
Certificate AuthorityPrice RangeVerification Level
DigiCert$300-500/yrOrganization validated
Sectigo (Comodo)$150-300/yrOrganization validated
GlobalSign$250-400/yrOrganization validated
SSL.com$150-250/yrIndividual/Organization
Entrust$300-500/yrEnterprise grade

[!TIP] For most businesses, DigiCert or GlobalSign offer the best balance of trust and support. Their certificates are on Adobe’s Approved Trust List (AATL).


When WPsigner finalizes a document with your Digital ID:

1. Document Hash Created
└─ SHA-256 hash of entire PDF content
2. Hash Encrypted
└─ Your private key encrypts the hash
3. Signature Embedded
└─ Encrypted hash + your certificate added to PDF
4. Timestamp Applied
└─ TSA server certifies the signing time
5. Sealed PDF Created
└─ Final document with digital signature

When someone opens the signed PDF in Adobe Reader:

1. Extract Signature
└─ Adobe reads the embedded signature
2. Verify Certificate
└─ Checks if CA is trusted (AATL)
3. Validate Hash
└─ Recalculates hash and compares
4. Check Timestamp
└─ Verifies signing time
5. Display Status
└─ ✅ Valid or ❌ Invalid

  1. Go to WPsigner → More → Digital ID
  2. Or navigate to WPsigner → Settings → Security

Option 1: Generate Self-Signed Certificate

Section titled “Option 1: Generate Self-Signed Certificate”

For testing or internal use:

  1. Click Generate Self-Signed Certificate
  2. Fill in the certificate details:
FieldDescriptionExample
Common NameYour name or companyAcme Corporation
OrganizationCompany nameAcme Corp
DepartmentOptional departmentLegal Department
CityYour citySan Francisco
State/ProvinceYour stateCalifornia
CountryTwo-letter codeUS
EmailContact emaillegal@acme.com
Valid YearsCertificate lifetime3 years
  1. Click Generate Certificate
  2. Certificate is created and activated immediately

For production use with purchased certificate:

  1. Obtain a .p12 or .pfx file from your CA
  2. Click Upload Certificate
  3. Select your .p12/.pfx file
  4. Enter the certificate password
  5. Click Upload and Activate
FormatExtensionDescription
PKCS#12.p12, .pfxContains private key + certificate
PEM.pem, .crtCertificate only (convert to .p12)
DER.der, .cerBinary format (convert to .p12)

WPsigner accepts .p12 and .pfx files directly.


The Adobe Approved Trust List is a list of Certificate Authorities that Adobe automatically trusts. When you sign with an AATL certificate:

  • Adobe Reader shows a green checkmark
  • Recipients see “Signature is VALID”
  • No manual trust configuration needed
  • Maximum legal credibility
  • DigiCert
  • GlobalSign
  • Sectigo
  • Entrust
  • IdenTrust
  • DocuSign (certificate program)
  • SwissSign

Self-signed certificates show:

  • Yellow warning triangle ⚠️
  • “Signature validity is UNKNOWN”
  • Recipient must manually trust your certificate

This is still legally valid but requires recipient action to verify.


PracticeWhy
Strong passwordProtect your private key
Secure storageStore .p12 file safely
Limited accessOnly authorized staff should access
BackupKeep secure backup of certificate
Regular rotationReplace before expiration
PracticeWhy
Centralized managementOne certificate for all documents
Document policyDefine which docs need signing
TrainingEducate staff on certificate importance
Audit loggingTrack certificate usage

Certificates expire. Plan ahead:

  1. Set calendar reminder - 60 days before expiration
  2. Budget annually - Include in IT budget
  3. Test new certificate - Verify before old expires
  4. Update WPsigner - Upload new certificate

  • Verify the password provided by your CA
  • Passwords are case-sensitive
  • No spaces before/after password
  • Convert to .p12 format using OpenSSL:
Terminal window
openssl pkcs12 -export -out certificate.p12 -inkey private.key -in certificate.crt
  • Purchase a renewal from your CA
  • Generate a new self-signed certificate
  • Upload the new certificate to WPsigner

Adobe shows “Signature validity unknown”

Section titled “Adobe shows “Signature validity unknown””

For self-signed certificates, recipients must:

  1. Click on the signature
  2. Click “Validate Signature”
  3. Choose “Trust this certificate”

┌─────────────────────────────────┐
│ Signed PDF │
│ ┌─────────────────────────────┐ │
│ │ [Signature Image] │ │
│ │ - Just a PNG image │ │
│ │ - No cryptographic seal │ │
│ │ - Can be modified │ │
│ └─────────────────────────────┘ │
│ ⚠️ No verification available │
└─────────────────────────────────┘
┌─────────────────────────────────┐
│ Digitally Signed PDF │
│ ┌─────────────────────────────┐ │
│ │ [Signature + Certificate] │ │
│ │ ┌───────────────────────┐ │ │
│ │ │ SHA-256 Hash │ │ │
│ │ │ Private Key Signature │ │ │
│ │ │ X.509 Certificate │ │ │
│ │ │ RFC 3161 Timestamp │ │ │
│ │ └───────────────────────┘ │ │
│ └─────────────────────────────┘ │
│ ✅ Signature valid. Document │
│ has not been modified. │
└─────────────────────────────────┘

Section titled “Do I need a Digital ID for legal signatures?”

For basic contracts in the US under ESIGN/UETA, a signature without Digital ID can be legally valid. However, a Digital ID provides much stronger legal protection and is recommended for:

  • High-value contracts
  • Regulated industries
  • International agreements
  • Long-term records

Can I use one certificate for multiple documents?

Section titled “Can I use one certificate for multiple documents?”

Yes. Your certificate is reused for all documents you sign. There’s no per-document cost or limit.

  • Previously signed documents remain valid (signature was valid at signing time)
  • New documents cannot be signed until you upload a new certificate
  • Consider timestamping to extend long-term validity

Yes, self-signed certificates create legally valid signatures. The difference is trust establishment - recipients must manually trust your certificate rather than relying on a third-party CA.