A Chilkat customer signed a PDF using the Chilkat API. There were no errors, and the output PDF seemed to be signed. Using the Chilkat API to verify the signed PDF was also successful. Chilkat could see the signature and validated it successfully. However, the signature in the signed PDF could not be seen in Adobe Acrobat DC. When the […]
This blog post describes the case where your application asks Chilkat to produce an LTV-enabled PDF signature by specifying “ltvOcsp” in the signing attributes, yet the signed PDF as viewed in Adobe Acrobat does not show the signature as being LTV enabled. For example, in Adobe Acrobat, an LTV enabled signature looks like this: You can see the message “Signature […]
Question: I need to sign a PDF with a certificate and a signed hash returned from a 3rd party. Answer: It’s possible, and it’s a feature that was introduced in the latest version of Chilkat (v9.5.0.96). However, it requires a well-defined REST API (or something similar) where Chilkat can make the REST API call from within the PDF signing process. […]
Open a PDF in Adobe Acrobat DC. Then without doing anything else, close the PDF. Does Acrobat ask to save changes even though you made no changes? If so, then it means that Acrobat auto-fixed a corrupt PDF.