Convert signed PDF to PDFA with Aspose.PDF for .NET - Signatures become invalid

Hi

We are trying to protect pdf documents that previously was signed using Aspose.Pdf.Facades.PdfFileSecurity:

var privilege = Aspose.Pdf.Facades.DocumentPrivilege.ScreenReaders;
var fileSecurity = new Aspose.Pdf.Facades.PdfFileSecurity();
fileSecurity.BindPdf(inputFile);
fileSecurity.SetPrivilege(privilege);
fileSecurity.Save(outputFile);
fileSecurity.Close();

When we convert signed file 2434_Input.pdf (81.4 KB) to pdf format - signature becomes invalid (2435_Output_pdf.pdf (79.4 KB)).
When we convert this file to pdfa format - signature replaced with single text (2435Output_pdfa.pdf (79.2 KB)).

Are there any technical reasons for this difference?
Whether the same behavior as for pdfa can be implemented for pdf?

Best regards
Yurii

@uaprogrammer

Thanks for contacting support.

As you have already reported this issue in other thread, so we have logged the issue as PDFNET-43455 in our issue tracking system, for the sake of correction.

We have logged an investigation ticket as PDFNET-43456 in our issue tracking system. Our product team will further look into this and share their feedback accordingly. As soon as we have some significant updates in this regard, we will let you know. Please be patient and spare us little time.

As the investigation ticket has been logged already, so for now, as a workaround, you may remove PDFA compliance from obtained output (2435Output_pdfa.pdf) by using following code snippet.

var doc = new Document(dataDir + "2434_Output_PDFA.pdf");
doc.RemovePdfaCompliance();
doc.Save(dataDir + "2434_Output_PDFAremoved.pdf");

For your reference, we have attached an output document as well. 2434_Output_PDFAremoved.pdf (78.6 KB)

We are sorry for the inconvenience.

Hi,

Could you provide us with the latest update on the PDFNET-43456 issue?

Thank you in advance.

Regards,
Oleh

@uaprogrammer

We regret to share that your mentioned issue is not yet resolved due to other issues logged prior to it. We have recorded your concerns and will definitely consider them during issue investigation. We will surely let you know as soon as we have some definite updates regarding its resolution. Please spare us a little time.

We apologize for the inconvenience.

Hi,

Aspose.pdf.dll 19.11

The bug is still reproduced.

Signed file to pdf format - signature becomes invalid.

Signed file to pdf/a-1b format - signature is replaced with single text (removed)

Hope you will support us on this issue.

Regards,

Oleh

@uaprogrammer

We really apologize for the inconvenience. The issue is not yet resolved however, we have recorded your concerns and will definitely inform you as soon as the issue is resolved. Please spare us some time.

Hi,

Could you inform us if there are any updates regarding the issue?

BR
Oleh

@uaprogrammer

Regarding PDFNET-43455, please use encryption before signing the PDF document as Adobe Reader does not provide facility to encrypt the PDF that is already signed. Furthermore, the issue (PDFNET-43456) is not yet resolved and still pending for analysis. We will surely inform you as soon as it is resolved. Please spare us some time.

We are sorry for the inconvenience.

Hello,

Could you share the issue’s status in Aspose?
Thank you in advance.

Best regards, Oleh

@uaprogrammer

We really regret to inform you that earlier logged ticket is not yet resolved. However, we have recorded your concerns and will surely let you once the issue is rectified. Please give us some time.

We are sorry for your inconvenience.

Hello,

Could you share the issue’s status in Aspose?
Thank you in advance.

Best regards, Oleh

@uaprogrammer

We are afraid that the issue PDFNET-43456 is not yet resolved. We will certainly inform you once it is fixed. Please give us some time.

We apologize for the inconvenience.