PdfProcessing: Provide API for enabling Long-Term Validation (LTV)

Telerik Document Processing Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Unplanned

Last Updated: 05 Aug 2025 07:58 by ADMIN

Nuno

Created on: 23 Jun 2022 06:59

Category: PdfProcessing

Type: Feature Request

PdfProcessing: Provide API for enabling Long-Term Validation (LTV)

From the Part 4: PAdES Long Term - PAdES-LTV Profile (ETSI TS 102 778-4) Specification:

"Validation of an electronic signature requires data to validate the signature such as CA certificates, Certificate Revocation List (CRLs) or Certificate status information (OCSP) commonly provided by an online service (referred to in the present document as validation data). If the document is stored and the signatures are to be verifiable long after first created, in particular after the signing certificate has expired, the original validation data may no longer available or there may uncertainty as to what validation data was used when the document was first verified."

Duplicated Items

PDF export - Digital Signature with TSA timestamp

5 comments

ADMIN

Dess | Tech Support Engineer, Principal

Posted on: 05 Aug 2025 07:58

Hello, Nuno,

Currently, the support for Long-Term Validation (LTV), PAdES, and advanced digital signature features in PdfProcessing remains unplanned and is not scheduled for development. Although other PDF-related features like PDF/A compliance are being worked on, LTV and PAdES require significant additional development and are tracked separately. I understand your frustration, as LTV and PAdES are indeed common requirements for organizations that need to ensure robust, standards-compliant digital signatures. The primary reason these features are not yet planned is a combination of technical complexity and prioritization based on overall customer demand.

I have escalated this feature to our Product Managment so it will be included for discussion during our next planning iteration. Note that features are prioritized according to the volume of customer feedback and votes on the public feedback portal. While there is recognition of the importance of these features, other requests with even higher demand or dependencies have taken precedence so far.

Your feedback is valuable, and detailed descriptions of your use case help shape future planning. I recommend voting for these feature requests and sharing your scenario in the feedback portal to increase visibility:

PdfProcessing: Add support for the PAdES-BES signature standard
PdfProcessing: Provide API for enabling Long-Term Validation (LTV)

I hope this information helps. If you need any further assistance please don't hesitate to contact me.

Regards,
Dess | Tech Support Engineer, Principal
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Nuno

Posted on: 04 Aug 2025 08:20

This is still unplanned? Even with the other developments being currently ongoing? (around PDF/A*)
I honestly can't understand the reasoning behind why such a common requirement for signed PDFs is still not even planned.

ADMIN

Dess | Tech Support Engineer, Principal

Posted on: 28 Jul 2025 06:37

Hi, Tim,

Thank you for the provided information and details about the functionality you need. We will consider it when this functionality comes to a planning iteration in future. Since this depends on the overall demand I would encourage you to cast your vote for the item in order to increase its priority. Make sure that you click the Follow button to get notified for any status changes.

I would ask you to continue any communication about the validity of the current digital signing in PdfProcessing in the forum thread you have already opened and keep this feature request for the topic it is expected to describe. Thank you for your understanding.

Regards,
Dess | Tech Support Engineer, Principal
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Tim

Posted on: 25 Jul 2025 16:19

I should elaborate: the PDF is properly signed using a valid x509 issued by a trusted CA. The issue is the timestamp on the signature is not generated by TSA, and the PDFProcessor doesn't seem to support that functionality.

It appears that it could be added to a 'signature dictionary', however I'm unsure how to do so manually.

Foxit validation:

PDF-X:

(Please forgive me if I've duplicated this post)

Tim

Posted on: 25 Jul 2025 15:53

Hello! I require the ability to generate long-term valid signed certificates.

- Are you required to use a specific TSA or follow a particular validation policy for your signed PDFs?
Yes, we do require this ability. We are required to generate digitally signed certificates that allow for validation of the signature and identity, as well as preventing alteration of the PDF. The current implementation protects against alteration, however the signature is not recognized. These PDFs must be validated by all modern PDF clients, anywhere in the world.

- Which PDF viewers or validation tools are you using to check the signatures?
Currently we are using: Foxit PDF, Adobe Reader and PDF-XChange. All three flag the Telerik signature as invalid.

- Is your primary goal to ensure long-term validation (LTV) or compliance with standards such as PAdES?
Our goal is to produce a long-term signed PDF that can be opened by any client and be recognized as a valid signature and no alteration made. PAdES seems to meet or exceed our requirements.