++Adding to the topic,
As mentioned by @Abambo , this may be related to unusual signature credentials.
This, however, doesn't necessarily mean that the credentials are invalidated due to the type of licensing (or subscription plans ) that are running on two different computer devices with totally different versions of Adobe Acrobat, and possibly with two totally different operating systems as well.
What is key, is to be able to differentiate the signing method that the user of the PDF document employed at signing time (i.e. using a smart card and a certificate authority to validate the certificate credentials, a self-signed digital signature certificate (manually created by the signing user at signing time), or using a trusted digital certificate to digitally sign documents that is readily available only in their personal or work computers (usually accessed via the certificate store if using MS Windows).
For instance, in the office computer, you can try a few approaches to properly work around verifying the validity of such digital signature.
So, first, you should manualy perform a Trusted Certificates Update in the office computer.
Second, with the PDF document opened in Acrobat, you should able to right-click on the signed signature field of interest and select "Show Signature Properties..."; the Signature Properties dialog windows will pop up =>> Pay close attention to the section below "Signer Info".
If the "Advanced Properties..." and "Show Signer's Certificate..." buttons appear greyed out ( or inactive), click on the "Validate Signature" button once.
The dialog window will refresh and now you'll notice that you are able to point and click on those buttons.
To rule out if there is an actual bad certificate or a certificate revocation issue, click on the "Advanced Properties..." button =>> the next dialog "Advanced Signature Properties" will pop up and will display relevant information on which Adobe Acrobat software version was used to sign the document (to include the Hash Algorithm and Signatute Algorith).
Last, if this dialog window doesn't show the appropriate info (or displays an error message or crashes the application), then this may be an indication that the certificate is not only bad but also that the PDF form itself may be having an issue with the JavaScript core interpreter when it executes the certificate revocation security checks.
However, from what you've described earlier this doesn't seem to be the case.
You may click on the "Show Signer's Certificate..." button instead =>> the "Certificate Viewer" dialog window will open up =>> go to the "Trust" tab, and verify if any of the Trust Settings for that certificate appear marked with a red "X".
If one or more settings appear with a red X =>> Click on the "Add to Trusted Certificates.." button =>> and checkmark all the settings provided to enable that certificate as a trust anchor =>> click OK to commit the changes and save the document beflre exiting Acrobat.
Doing this will eliminate the certificate revocation checking every time that signed document is opened with any version of Adobe Acrobat, which in my very humble opinion, this looks like what you're currently struggling with.
4
Replies
AdChoices