Skip to main content
dadybear1234
Inspiring
June 14, 2025
Question

Establish trust with Adobe, Can't add Proof.com's Digital Sinature

  • June 14, 2025
  • 1 reply
  • 189 views

Greetings,

I had to sign some legal documents the other day. They had to be verified by a notary. Since I'm currently living at an SNF and have no car, too ill at the moment to travel to the attorney's office. So They use peroof.com an online video conference where at the other end is a Notary Public whoo's company proof.com has a registered digital signature that should be in a way attached to each document I signed, and there were several and when these PDFs are open in Adobe any user looking at them can find out inside Adobe if they were digitally signed. The problem being so far at least for whatever reason Adobe doesn't automatically recognize proof.com's digital signature. Every one of those documents opened in Adobe at the top in a blue strip reads: At least one signature has problems. There's a way to take proof.com's trusted certificate and add it to the first one of two IdenTrust Global Common Root CA 1 into Adobe repeat steps 6 - 9 and add the second  IdenTrust Global Common Root CA to Adobe and that blue strip disappears and now if you want you can check inside Adobe to find out they are digitally signed. However, the directions I was given did not work. I went to Adobe and looked this up in a similar way to the above and they would be digitally signed. I know for a fact that they are digitally signed. My attorney and proof.com both assured me they were. However, I want it to officially say that in Adobe. Again Adobe's and Proof's directions didn't work. Does anybody have an idea how to add these digital signatures?

1 reply

creative explorer
Community Expert
Community Expert
June 20, 2025

@dadybear1234 Sorry to hear that you are going through so much at the SNF.

Sometimes, even when the correct certificates are added, Adobe needs a little extra nudge to fully trust them. One common workaround, if you haven't already tried it, is to directly download the .fdf file from Proof.com (they often provide a specific file for establishing trust in Adobe) and import it into Adobe's "Trusted Identities" settings. If their initial instructions or Adobe's help pages didn't quite work, reaching out to Proof.com's technical support one more time, specifically mentioning that the IdenTrust Global Common Root CA import isn't resolving the "signature problems" message in your Adobe application, might help. They may have a more tailored solution or be able to walk you through a slightly different set of steps for your specific version of Adobe Acrobat.

m