Greetings,
I'm developing a poor-man's e-signing solution for my company. We store PDF contract templates as AZ Blobs. When we need to sign one of these contracts, we pull the template and merge the relevant data. An Angular/.NET Core application is then used to display this file and gather signatures from both parties. We then send the resulting PDF to both parties.
Everything seems to be working just fine. The only problem is that when the PDF is opened in Acrobat or Acrobat Reader, a notifcation is display stating that at least one signature has problems.
Further inspection showed that the certificate had expired. We were using the cert that Syncfusion includes. When looking at this cert's details, we saw that the Intended Usage was Code Signing, so we tried to use an actual Comodo code signing cert that we have. This time we got a similar notification but this time the Signature was invalid because the Signer was unknown or not included inthe list of trusted certificates.
We even tried creating a Digital Id using Adobe Acrobat but, as expected, if the signed PDF is opened on the machine where the Id was created, everything looks ok, but if opened on any other machine, the same notification described above is shown.
Our question is, is there something we can do so that our signed PDFs won't trigger this notification, especially when seen by the other parties? If there's something that can be done, would you please orient us towards the solution?
Thanks in advance!
