Home / Blog / Tutorials

Signature Not LTV Enabled? Keep PDF Signatures Valid After Expiry

What "Signature is not LTV enabled and will expire after" means, how timestamps and embedded revocation data keep signatures valid for years, and how to repair signed files.

A signed PDF that shows a green tick today can show a warning next year. The two messages people search for are "Signature is not LTV enabled and will expire after" a given date, and the complaint that a signature "became invalid" once the signer's certificate expired. Both come from the same gap: the PDF does not carry the evidence a validator needs to check the signature later. This post explains what that evidence is, how to add it when signing, and how to repair documents that are already signed.

Why a valid signature can stop validating

To accept a signature, a validator needs to prove three things:

  1. The signed bytes have not changed.
  2. The signer's certificate chains to a trusted root.
  3. The certificate was valid and not revoked at the time of signing.

Point 3 is the weak spot. Without extra data, the validator only has the signer's computer clock as the signing time, which proves nothing, and it has to go online to ask the CA whether the certificate was revoked. Years later, the certificate has expired, the CA may have retired that OCSP responder or CRL, and the validator may be offline. It then cannot answer point 3 and reports the signature as unknown or invalid.

Two additions close the gap:

  • A trusted timestamp (RFC 3161) from a Time Stamping Authority proves when the signature existed. The validator can then check the certificate's status at that moment instead of today.
  • Long-Term Validation (LTV) data: the certificate chain plus OCSP responses or CRLs, stored inside the PDF (in a structure called the Document Security Store). The validator no longer needs to reach the CA.

A signature that has both is what Acrobat calls "LTV enabled". The PAdES standard names the levels: B-B (basic signature), B-T (with timestamp), B-LT (with validation data), and B-LTA (adds a document timestamp over everything, so the evidence itself can be renewed before the timestamp authority's certificate expires).

Reading the Acrobat message correctly

"Signature is not LTV enabled and will expire after <date>" does not mean the signature is broken. It means: "this signature is valid now, but once the certificate's validity ends on <date>, I will not be able to validate it from the file alone." Treat it as a warning for documents that must remain verifiable: contracts, invoices kept for tax audits, certificates of conformity, regulatory submissions.

Adding timestamp and LTV when signing in Acrobat

  1. Menu > Preferences > Signatures > Document Timestamping > More (classic interface: Edit > Preferences; macOS: Acrobat > Preferences): in Server Settings, select Time Stamp Servers > New and add a timestamp server. Use the TSA of the CA that issued your certificate; common public ones are http://timestamp.digicert.com, http://timestamp.sectigo.com, http://ts.ssl.com and GlobalSign's http://timestamp.globalsign.com/tsa/r6advanced1. Select it and click Set Default.
  2. Menu > Preferences > Signatures > Creation & Appearance > More: tick Include signature's revocation status.
  3. Sign with network access, so Acrobat can fetch OCSP/CRL data and the timestamp.
  4. Check: in the Signature Panel, expand the signature. You should see "Signature is LTV enabled" and "Signature is timestamped".

If revocation fetching fails at signing time (firewall, proxy, OCSP outage), Acrobat signs anyway and the result is not LTV enabled. Check outbound access to the CA's OCSP and CRL URLs (they are listed in the certificate's "Authority Information Access" and "CRL Distribution Points" fields).

Repairing a document that is already signed

Case A: signed with a timestamp, but no LTV data

This can usually be fixed, as long as the CA's revocation services still answer. In Acrobat, right-click the signature and choose Add Verification Information, then save. Acrobat fetches the chain and revocation data and appends them as an incremental update, so the signature stays intact. Acrobat only offers this option when the signature is valid, chains to a trusted root (not a self-signed or manually trusted certificate), and the verification time is not set to the current time. To protect that evidence for the long term, add a document timestamp afterwards: All tools > Use a certificate > Timestamp in the current Acrobat interface, or Tools > Certificates > Time Stamp in the classic interface. The document timestamp comes from the default timestamp server configured above; without one, Acrobat falls back to the computer's clock.

Case B: no timestamp at all

While the certificate is still valid, you can add LTV data, but the signing time still comes from the signer's clock, and some validators will still reject it after expiry. A document timestamp added now proves the signature existed now, which helps, but it cannot prove an earlier signing time. For important documents the clean solution is to re-sign with timestamp and LTV enabled, before the certificate expires.

Case C: the certificate has already expired

Without a timestamp there is nothing to anchor the validation to a time when the certificate was valid. You cannot fix this after the fact. Re-sign with a current certificate.

Common reasons LTV still shows as "not enabled"

  • Verification settings differ: in Menu (or Edit) > Preferences > Signatures > Verification > More, the option "Verify signatures using" (signing time, embedded timestamp, or current time) and "Require certificate revocation checking to succeed" both influence whether Acrobat reports LTV. The same file can show different results on two machines.
  • The timestamp itself is not covered: the TSA's certificate also needs revocation data. Some tools embed data only for the signer's chain.
  • The root is not trusted by Acrobat: LTV cannot make an untrusted chain trusted. Fix trust first (see Signature validity is UNKNOWN).
  • The file was rewritten after LTV data was added, discarding the appended data or breaking the signature.

The same rule for code signing

Authenticode works the same way. A signed EXE without a timestamp becomes "not valid" when the code-signing certificate expires. With a timestamp it keeps validating. Always sign with an RFC 3161 timestamp:

signtool sign /sha1 <THUMBPRINT> /fd sha256 /tr http://timestamp.digicert.com /td sha256 MyApp.exe
signtool verify /pa /v MyApp.exe

A file that was signed without a timestamp, while the certificate was still valid, can be timestamped later without re-signing:

signtool timestamp /tr http://timestamp.digicert.com /td sha256 MyApp.exe

Use /tr with RFC 3161 URLs and /t only with legacy Authenticode timestamp URLs; mixing them up is a common cause of "the specified timestamp server either could not be reached or returned an invalid response".

Checklist for documents that must last

  • Certificate from a CA your recipients trust (AATL for Adobe).
  • RFC 3161 timestamp from your CA's TSA on every signature.
  • Revocation data embedded at signing (LTV).
  • For archives kept beyond the TSA certificate's life, add a document timestamp periodically.
  • Do not modify the PDF after signing except through incremental updates.

How OneSigner handles it

In OneSigner every PDF signing profile has a Timestamp URL and an LTV option. Set both once, and every document signed through the watched folder, REST API or portal is timestamped and carries the chain and revocation data, so it still validates after the certificate expires. The signing machine needs outbound HTTPS to the TSA and the CA's OCSP/CRL servers. Code-signing profiles and OneSignTool use an RFC 3161 timestamp as well. See signing profiles and the setup guide.

Have a question about this?

Email the team that wrote it, and we will reply directly.