Hello.
When I sign a pdf (attached in this message) with Pkcs7Signature attached, when it view with Acrobat Reader 8 it shows correct but with Acrobat Reader 9 o later does not show.
What can i do to resolve this issue?
Thanks.
Hi,
Thank you for the details.
Well, it seems a very strange issue. Please share your template file, sample code and certificate file with us. This will help us identify the issue and resolve it soon.
Sorry for the inconvenience,
Hi,
Template file is doc.pdf
Certificate file is cert.rar
Sample code:
Dim osign As New Aspose.Pdf.Kit.Pkcs7Signature(“c:\temp\cert.p12”, “sIikZSmz”)
Dim rect As New System.Drawing.Rectangle(430, 740, 100, 100)
Dim oPDFSign As New Aspose.Pdf.Kit.PdfFileSignature(“c:\temp\doc.pdf”)
oPDFSign.CertificationLevel = Aspose.Pdf.Kit.PdfFileSignature.CertifiedNoChangeAllowed
oPDFSign.Sign(1, “REASON”, “CONTACT”, “LOCATION”, True, rect, osign)
oPDFSign.Save(“C:\temp\sign.pdf”)
With Acrobat Reader 8 I can see signature digital but in Acrobat Reader 9 or later I can’t
Thanks.
Hi,
Thank you for sharing the sample code and certificate file.
I am able to generate an issue regarding applying signature to your provided template document using the latest version of Aspose.Pdf for .NET v6.6. The issue has been registered in our issue tracking system with issue id: PDFNEWNET-33226. You will be notified via this forum thread regarding any update against your issue.
Sorry for the inconvenience,
Hello.
I would like to know how is this issue.
Thank you.
Hi,
Well, I am afraid the issue is not resolved yet. However, I have requested the development team to share an ETA regarding the resolution of the issue. As soon as I get a response, I will update you via this forum thread.
Sorry for the inconvenience,
Hi,
The development team is investigating your issue and I would like to share findings with you.
This issue is rather complex as it concerns the way Adobe Reader/Acrobat opens PDF documents. The error you see on opening a signed PDF document does not mean there is a problem with Aspose.Pdf, but Adobe Reader/Acrobat may consider some aspects wrong. Aspose.Pdf has been tested and the signed PDF is opened in Foxit (and in other PDF readers) without any problems. So, what can be strange or suspicious for Adobe Reader/Acrobat? The original PDF document (doc.pdf) has a dynamic XFA form, meaning the document does not have any standard PDF field. However, signing adds one standard PDF field (the signature field). This situation can be logically incorrect.
Adobe Acrobat does not even allow adding a signature into the PDF with an XFA form. Additionally, after adding the signature field, the PDF document loses extended user rights—meaning the form can’t be filled using Adobe Reader.
Our development team is further investigating this issue to fix it. I will keep you posted via this forum thread.
Sorry for the inconvenience.
Hello.
I would like to know how is this issue.
Thank you.
Hi,
Thanks for your patience.
I have verified the status of this issue from our issue tracking system and regret to share that this issue is still unresolved. Currently our team is working on this issue. Also, at the moment we can't provide you the ETA for this issue. However, I have requested the development team to share the ETA regarding its resolution. As soon as we get required information, we will be more than happy to update you with the status of correction. Please be patient and spare us little more time.
We are really sorry for the delay and inconvenience.
Thanks & Regards,
The issues you have found earlier (filed as PDFNEWNET-33226) have been fixed in Aspose.Pdf for .NET 9.3.0.
Blog post for this release can be viewed over this link
This message was posted using Notification2Forum from Downloads module by Aspose Notifier.