Electronically signed documents

[miłosz_6545]

Hello,

I have a problem with electronically signed documents.
Opening them in Windows on a user account containing Polish characters shows a signature verification error message (attachment 1).
When opening the same document on an account without Polish characters everything verifies correctly.
I am also attaching debug.log (attachment 2).

Have any of you had this problem before? I would like a solution that does not require, for example, the creation of a new user.

[creative explorer]

@miłosz_6545 it sounds like a font issue or a charcter encoding mismatch. 

You could try this work-around, create a simple folder. On your C: drive (or any drive), create a new folder with a very simple name, like C:\TempPDFs or C:\PDFDocuments. Avoid any special characters, spaces, or non-ASCII characters in this folder name. Before opening the electronically signed PDF, copy or move it into this newly created simple folder (e.g., C:\TempPDFs\YourSignedDocument.pdf or C:\PDFDocuments\YourSignedDocument.pdf ). Now, open the PDF document directly from this simple folder. 

1. When you open the document from C:\TempPDFs or C:\PDFDocuments , Adobe Acrobat (and the underlying Windows processes it uses for signature verification) will primarily interact with this simplified path, avoiding the complex characters in your user profile directory. This can often prevent the encoding conflict that leads to the verification error.
   
   Let me know how it goes. 

[miłosz_6545]

I tried your suggested solution, but Adobe still shows the message ‘There was a problem with at least one signature’.

[MikelKlink]

Considering the log file you shared,

[0702/131255.889:ERROR:context.cc(151)] The cache_path directory (C:\Users\Mi�osz Rychlewicz\AppData\LocalLow\Adobe\AcroCef\DC\Acrobat\Cache) could not be created.
[0702/131255.899:ERROR:context.cc(166)] The cache_path is invalid. Defaulting to in-memory storage.
[0702/132506.202:ERROR:context.cc(151)] The cache_path directory (C:\Users\Mi�osz Rychlewicz\AppData\LocalLow\Adobe\AcroCef\DC\Acrobat\Cache) could not be created.
[0702/132506.213:ERROR:context.cc(166)] The cache_path is invalid. Defaulting to in-memory storage.

there indeed appears to be a shortcoming in Acrobat in respect to paths with interesting characters.

BUT in the end Acrobat in the log excerpt switched to in-memory storage. Thus, these errors should not cause validation issues, should they?

[miłosz_6545]

However, there is a problem with signature validation. I am not an Adobe expert, so I don't know why this is the case.
I have noticed a dependency with Polish characters.

[Meenakshi Negi]

Hi miłosz_6545,

Thank you for reaching out.

Did you try to validate the signature? Please refer to the information in the following help document:https://adobe.ly/4lb5hlHl. 

We will need the file to determine what is causing this behavior. If possible, please share the file so we can try to replicate it. 

Let us know how it goes.

Thanks,

Meenakshi

[miłosz_6545]

Unfortunately the link you sent does not work, error 404

[Meenakshi Negi]

Hi miłosz_6545 ,

Sorry about the typo.

Please refer to the following page: https://adobe.ly/4kwE3Fe.

Thanks,

Meenakshi

[miłosz_6545]

Hi,

I have tried to do as per the attached screenshot, however nothing happens.
I think it needs the paid version of Adobe for this, I use the free one.

[MikelKlink]

In the situation of the screenshot in your original posting, have you opened the signature panel? What does it show?

[miłosz_6545]

I selected the option highlighted in the screenshot.
Unfortunately nothing happens, still a message about a problem with the signature.

[MikelKlink]

What does the "Panel Podpis" (click button on the right of the screen shot in your original posting) show?

[miłosz_6545]

Attached

[MikelKlink]

Ok, according to Google translate the issue is that the identity of the signer is unknown because it is not on your trusted cert list.

If, as you say, that issue does not occur when you log in with a user name without special characters, chances are that here again Acrobat internationalization is deficient: Maybe it cannot read the list of trusted certificates from the Acrobat data within your user folder at all. Or it merely cannot update them and you have an outdated trust list.

@Meenakshi Negi for reproducing the issue you may want to create a test Windows user with @miłosz_6545 's name. In particular make sure you use the 'ł' with the stroke, U+0142.