10.7 Digital Signature Issues

[mbahen@wrallp.com]

Greetings,

Having issues in the new 10.7 build 398 version trying to use the 'Sign Document' tool in XChange editor. When the Sign Document window pops up the Select Certificate (Digital ID) window is blank. Refreshing the display doesn't make the certificate show up either. If we click on the Manage Button we see the Certificates in Windows Digital IDs section. We tried creating a new Digital ID using the 3rd party certificate file to import again but no certificate doesn't show up in the "Sign Document" window. (Does appear in the Manage -> Digital IDs after re-importing). That windows seems to stay blank. Understanding the 10.7 changed how Digital IDs and Signatures work but would appreciate some clarification (Help documentation shows the old Signature window)

Anyone know of a way to get 3rd party Certificates from the Windows Certificate Store to show up in the Sign Document -> Select Certificate window?

Thank you!

[Daniel - PDF-XChange]

Hello, mbahen@wrallp.com

We are investigating a few such cases, if you could help us by logging your process. In this case specifically, opening the "sign document" window, and clicking the "manage" button for a moment, to show the difference between the ID list there, and what certificates are available in the previous window, that would be perfect.

Also, if you are able to record a video of the process as you are using Debug view, that would help the Dev team to navigate the logs, as we can use the timestamps to quickly identify problem points. That video can be uploaded alongside the log file.
Here is a portable debug version of the Editor 10.7, with additional logging for certificates: [check your email please]

Short instructions:
1. Extract the archive to any folder.
2. Run `DbgView.exe` from that folder - it is Microsoft's utility for collecting debug outputs
3. Run the Editor from that folder.
4. Create a new document and try to sign it.
5. When done (successfully or not), save the log from Debug View (File -> Save As...) and upload it here:
[check your email please]

Kind regards,

[wrhiltz]

Having a similar issue.

Connected pdf-xchange to Azure RCM. Permissions granted and I presume that Azure certificates were installed.

Decided not to use RCM.

Removed Azure plug-in from pdf-xchange.

Cannot use my own ID-Trust Digital IDs . Unable to remove other digital ids.

See IMG 1 and IMG2

Bill

[Daniel - PDF-XChange]

Hello, wrhiltz

We have managed to locate what we believe is the core problem with the issue now, and have already send out a new debug version to a few individuals.
I will pass one along to you as well, with the necessary instructions, if you would like to test it and share your results with us.

If all goes well and we get a few more positive replies about the latest debug version, we should see build 10.7.1 released next week (Hopefully on Monday).

Kind regards,

[fromans_swpa]

Daniel, we are having the same issue here. Digitial signatures that were previously working are now broken and unavailable for use in 10.7, despite seeing them listed in the Windows Digital IDs. I would like to test that new build if possible. Thanks!

[Dimitar - PDF-XChange]

Hello fromans_swpa,

Welcome to our Forum.

As Daniel mentioned, the problem will be resolved in the next version, which will be released this week.

Regards.

[fromans_swpa]

Sorry, I didn't see that final response before I posted. Please note the use case you mentioned you were trying to fix is exactly what we have here and was broken with this update. Specifically, digital signatures using derived credentials on Yubikeys (PIV-D) generated from the certificate on our smart cards (PIV).

[Daniel - PDF-XChange]

Hello, fromans_swpa

Version 10.7 has much more robust security features, but some of those it seems were over-sensitive. Build 10.7.1 should be coming out later today or tomorrow, as we are on schedule, last I heard. The incoming fixes should address both;

1. Cases of certificates that previously worked, and are now missing from the list placement list, as well as...
2. Many of those that are visible, but provide some error (often citing permissions) during placement.

It also makes some minor changes to the validation system to address a number of cases with existing/already placed signatures in viewed PDF files, improperly claiming they are "unsupported" or "unknown" instead of the normal "valid/invalid/not verified" states.
These changes should address the problems you are seeing, but with the complete overhaul of the signing system, there are some areas we simply could not test locally. We sincerely apologize for the inconvenience caused by the 10.7.0 release, and are working to get it resolved as quickly as we can.

The previously mentioned Debug build is no longer available, as it is too late for new data from that one to be applied to the 10.7.1 release coming soon. Please keep an eye out for 10.7.1 (tonight/tomorrow), and if you still experience issues after the update, get in contact with is immediately via <Support@PDF-XChange.com>, with a link to this post. If there are any more issues, a new debug build will likely be created promptly.

I should note that there is one known issue with the next release that will take additional time to address. Users of older externally stored "PFX" files (most commonly those created by Adobe), may encounter errors stating the PFX format is not supported. This is an extension of the aforementioned "overly sensitive" security features. We are working on a solution for that, but in the meantime, the best solution I can suggest for those users, is to create a new self signed PFX file, or contact the certificate creator, to ask for a version which can be installed locally to the windows system store.

Kind regards,

[zeta automation gmbh]

Dear PDF-Exchange Team

Since the update to the new version 10.7, our previously deployed certificates can no longer be used for signing documents. While the certificates are visible in the Windows certificate store for the users, they are not shown in the selection list for signing.

Could you please provide us with an estimated timeline for the release of a new version that will enable existing certificates to appear in the certificate list and allow them to be selected for use?

Thank you in advance for your assistance!

Best regards,
MP

[lev]

An updated came out 2 days ago. Is digital signing still not working after the update?

image.png

[Dimitar - PDF-XChange]

Hi,

The problem is fixed in version 10.7.1.399.

Whoever has this problem needs to update their product to the latest version.

Regards.

[Mathew]

The problem is fixed in version 10.7.1.399.

Lightly off-topic but the version history for 399 has a typo:

image.png

https://www.pdf-xchange.com/product/pdf ... 10.7.1.399

[Daniel - PDF-XChange]

Hello, Mathew

Yes, that was reported yesterday as well, I was under the impression that it was supposed to have been fixed by now, but in looking back it may have ended up buried below other discussion. I would update it myself, but I do not have the permissions to edit that part of the site, so I have nudged the dev team once again.

Sorry for the confusion!

Kind regards,