Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

10.11.6 broke digital signing in Adobe?

Updating to 10.11.6 seems to have broken signing Adobe documents with digital certificates. Anyone else having this issue? All trusted roots and certificates are trusted by Adobe and the System Keychain and the certificates show as valid but when trying to sign a document this error always pops up - Error encountered while signing: The credential. selected for signing is invalid.


Message was edited by: walkerap

OS X El Capitan (10.11.6), null

Posted on Jul 27, 2016 12:08 PM

Reply
Question marked as Best reply

Posted on Jul 28, 2016 9:35 AM

I am having the same issue on multiple systems. However, not all my 10.11.6 systems are having this issue. So, I went through the signing process on both systems and captured the logs. There was only a few noticeable differences between the two. On the system that IS working the following log entries are present, but they are not present in the system NOT working.


7/28/16 9:09:49.634 AM WindowServer[2852]: disable_update_timeout: UI updates were forcibly disabled by application "Acrobat Reader" for over 1.00 seconds. Server has re-enabled them.

7/28/16 9:09:51.020 AM WindowServer[2852]: common_reenable_update: UI updates were finally reenabled by application "Acrobat Reader" after 2.39 seconds [0.42fps] (server forcibly re-enabled them after 1.00 seconds [1.00fps])


I have no idea what this means, but I am hoping someone reading this might be able to use this info to help solve the problem.

30 replies
Question marked as Best reply

Jul 28, 2016 9:35 AM in response to walkerap

I am having the same issue on multiple systems. However, not all my 10.11.6 systems are having this issue. So, I went through the signing process on both systems and captured the logs. There was only a few noticeable differences between the two. On the system that IS working the following log entries are present, but they are not present in the system NOT working.


7/28/16 9:09:49.634 AM WindowServer[2852]: disable_update_timeout: UI updates were forcibly disabled by application "Acrobat Reader" for over 1.00 seconds. Server has re-enabled them.

7/28/16 9:09:51.020 AM WindowServer[2852]: common_reenable_update: UI updates were finally reenabled by application "Acrobat Reader" after 2.39 seconds [0.42fps] (server forcibly re-enabled them after 1.00 seconds [1.00fps])


I have no idea what this means, but I am hoping someone reading this might be able to use this info to help solve the problem.

Aug 11, 2016 7:59 AM in response to walkerap

The same is happening to me when using both Acrobat Reader DC and Acrobat Pro together with the Portuguese Citizen Card (that holds the certificates for digital signing).


I don't know how many people are being affected by this issue, but if all the Portuguese Citizen Cards are not functioning since the update, this is a major issue for businesses and government transactions in Portugal that fully rely on digital signatures.


Hope a fix comes soon.

Aug 11, 2016 8:38 AM in response to m.ferreira

Anyone who uses a PKCS11 module might be able to fix by following along with:


Got digital signing working again. Had to add the CACKey PCKS#11 module (what Firefox uses) to Adobe Reader:


Instructions:

- Preferences —> Signatures —> Identities & Trusted Certificates —> More…

- Click "PKCS#11 Modules and Tokens”

- Click “Attach Modules”

- Enter path to your PKCS#11 module; for CACKey this is /Library/CACKey/libcackey.dylib

- Click “OK”

- Click the little triangles to open up the module until you see the card

- Click the card

- Click on the email signing certificate (look for one issued by DOD EMAIL CA-xx and includes Intended usage of Digital Signature)

- Click the “Usage Options” popup menu and select “Use for Signing”

- Click Close, then Click OK.

Aug 11, 2016 9:36 AM in response to walkerap

Thanks for the information jnojr. This works for some users but unfortunately this does not fix systems which utilize Centrify for CAC authentication. Installation of CACKey breaks Centrify and installing the PKCS11 module installed by Centrify results in an error along the lines of "the module could not be loaded." Apple, Adobe, someone really needs to address this situation soon. The ability to sign documents is a major work stoppage.

Aug 11, 2016 9:53 AM in response to rde@vick

Understood, I'm in the same boat... we use PKard which also doesn't supply a PKCS11 module. This is one thing I hate... they say "We won't do that because the correct way to handle this stuff is with Keychain", while Mozilla, most notably, says, "We won't use Keychain because it isn't OS-agnostic, they should support PKCS11!"

Aug 11, 2016 2:47 PM in response to walkerap

It's really unfortunate to have this issue and neither side knows how to fix it. I've spent hours with Adobe in my computer and on the phone just to have them elevate my issue 3 times....still not fixed. Then to chat with Apple support and the only result was for me to install a program so they could monitor my Mac....no thanks. Fix it please so I'm not wasting more time and money.

Aug 11, 2016 8:49 PM in response to walkerap

Hello everyone,

Software updates do not happen like they did in the past. All companies release updates very frequently and they are not going to be tested with 3rd party software. Often these updates are meant to address possible security exploits. Anyone who depends on any software needs to perform their own testing before updating any critical systems. Neither Apple nor Adobe will do this testing for you. There is no point in wasting your time complaining about it. This is the new normal.

10.11.6 broke digital signing in Adobe?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.