Populating field forms in a signed PDF

I have a PDF that has a form in it. The PDF is signed with a certificate. If I populate the form using Aspose I then save the PDF and the Certificate is then removed from the PDF and the PDF is then shown as created by Aspose. Is there a way to use Aspose.PDF to populate the PDF in C# and retain the certificate signed status?

Thanks

@RobertMOswald

Could you please share your sample PDF document and sample code snippet for our reference. We will test the scenario in our environment and address it accordingly.

        string src = @"C:\Projects\caform.pdf";
        string dest = @"C:\Projects\caform-saved.pdf";

        if (new FileInfo(dest).Exists) new FileInfo(dest).Delete();

        // For complete examples and data files, please go to https://github.com/aspose-pdf/Aspose.Pdf-for-.NET
        // The path to the documents directory.
        //string dataDir = RunExamples.GetDataDir_AsposePdfFacades_Forms();

        // Create Form Object
        Aspose.Pdf.Facades.Form pdfForm = new Aspose.Pdf.Facades.Form();

        var fields = new Dictionary<string, string>
        {
            {"name", "form1[0].Page1[0].PersonalDetails[0].Name[0].FamilyName[0]"},
            {"validate", "form1[0].Page1[0].ButtonsHeader[0].ValidateButton[0]"}
        };

        // Open Document
        pdfForm.BindPdf(src);
        var existingFields = pdfForm.FieldNames;

https://www.canada.ca/content/dam/ircc/migration/ircc/english/pdf/kits/citizen/cit0001e-2.pdf
// Fill the field “textfield” with “Mike”.
pdfForm.FillField(fields[“name”], “Mike”);

        // Save updated file
        pdfForm.Save(dest);

@RobertMOswald

We have tested the scenario in our environment while using Aspose.PDF for .NET 21.1 and noticed that the output PDF was showing secured when opened in Adobe Reader. Is it not the case at your side? Please share a screenshot of the issue related to the missing certificate in the PDF file so that we can further proceed accordingly.

output.pdf (3.1 MB)

Regarding showing Aspose.PDF as producer or creator, please note that it is expected behavior as per the policy that Aspose.PDF for XXX will be shown in the document properties against producer, creator fields and it cannot be changed or modified.

Please can I ask you to confirm with the following PDF. For some reason the other PDF did not appear to have a certificate for some reason.
caform.pdf (672.7 KB)

@RobertMOswald

We were able to notice the issue with the PDF that you have now shared. We have tested the scenario using Aspose.PDF for .NET 21.1 and logged an issue as PDFNET-49388 in our issue tracking after replicating it. We will further look into its details and keep you posted with the status of its correction. Please be patient and spare us some time.

We are sorry for the inconvenience.

Is there any feedback regarding this issue yet?

@RobertMOswald

The issue has been recently logged in our issue tracking system and we are afraid that it is not yet investigated. Please note that it will be analyzed and fixed on first come first serve basis as per free support policies and we will surely inform you as soon as additional updates are available in this regard. Please give us some time.

We are sorry for the inconvenience.