Another Disappearing Signature Situation

There are a number of errors in your Initial_withSigField.pdf file, in particular:

• The signature field widget annotation of your document page is a direct object in the Annots array of the page object.
  This is wrong, the Annots array shall contain indirect references to all annotations associated with the page (ISO 32000-2 Table 31 — Entries in a page object). 
• Also this widget annotation is merged with its field, so the field object also is only present as direct object in the page Annots. But again each field in a document’s interactive form shall be defined by a field dictionary, which shall be an indirect object (ISO 32000-2 section 12.7.4 Field dictionaries).
• The signature field widget annotation of your document page in its P entry does not point back to your document page object but instead to another page dictionary that is not included in your document Pages tree, i.e. an unused, orphan page.
  Furthermore, this orphan page object in its Annots does not reference the signature field widget annotation of your document page; it actually cannot do so because that annotation is not an independent indirect object but merely a direct object. Instead the orphan page references yet another signature field widget annotation object.
• The signature field is not referenced from the Fields array of the AcroForm dictionary of the document; it actually cannot because the signature field is not an independent indirect object but merely a direct one. But the Fields array is specified to be the array of references to the document’s root fields (those with no ancestors in the field hierarchy) (ISO 32000-2 Table 224 — Entries in the interactive form dictionary).

This results in a number of errors in Final.pdf, too, a garbage-in, garbage-out situation. All one can blame Adobe Acrobat for in this context, is that it attempts to sign this broken structure instead of rejecting it.

Hi,

Well, I don't have Acrobat Standard, but I tested your PDFs with Acrobat Pro DC and encountered the same issue.

I am not sure if you were aware that for the past three years Adobe have been announcing end of support for Type 1 Fonts.

See here:

• https://helpx.adobe.com/fonts/kb/postscript-type-1-fonts-end-of-support.html

I was able to see this clearly when I try to edit your PDF and add another field object. The signature field together with the new object disappeared and didn't save the changes at all.

So, I opened both your original "PDF Final" document and compared the Document Properties against my edited copy, and indeed, the Type 1 Font was not substituted nor embedded ... everything just disappeared (and I also opened the same test file with a web browser and nothing there).

Only the Tahoma True Type Font appeared embedded in my blank test document but no signature field whatsoever (completely gone).

This in particular, may be related to a lost security restriction after the PDF was processed with PdfPig (just guessing in the blind here).

So, this brings me to ask you if the .Net library that PdfPig is using to produce PDFs is up to date to its latest version.

But in particular, see this wiki of PdfPig with emphasis on Document Creation that was posted in GitHub:

"

The PdfDocumentBuilder creates a new document with no pages or content. First, for text content, a font must be registered with the builder. Currently this supports Standard 14 fonts provided by Adobe by default and TrueType format fonts.

To add a Standard 14 font use:

public AddedFont AddStandard14Font(Standard14Font type)

Or for a TrueType font use:

AddedFont AddTrueTypeFont(IReadOnlyL

• https://github.com/UglyToad/PdfPig/wiki/Document-Creation

That said, see this other link at the beginning of the same topic:

• https://uglytoad.github.io/PdfPig/

My main question is if you had PDF that was created in Acrobat first with a digital signature field using the Prepare Form tool; and then you signed the PDF document immediately before PdfPig produced the final PDF document?

If that was the case, I would say to produce the PDF first with PdfPig, and lastly certify the document with a digital signature using the Certificates tool instead.