Problem of this kind usually happens when the driver that supports your token does not fully conform to all applicable standards. Some signing applications are lenient to some of the mismatch and you can still use your token for signing in those apps. Acrobat is more stringent about it.

Without actually having your token it is difficult to investigate further.

I think Gabi Gavrila is using a SafeNet product, like SafeNet Authentication Client as eToken driver. I'm sure, the drivers/devices provided by SafeNet are fully conform with the applicable standards, at least they didn't have any issue signing PDF documents until last week.

The above reported problem started to appear with version Adobe Acrobat Reader DC 15.016.20039. Some older versions of Adobe does work continuously without giving any error message.

My team has been working on this issue for several hours and we finally found a fix. I don't know what you're using for your signature, but we use our Smartcards which rely on a software called ActivClient (Military / DoD uses this type).

In order to make this error go away, we had to update our ActivClient installations from version 6 to version 7.

We have updated the SafeNet Authentication Client to the latest available (10.0.43.0) on Windows and the problem still persists. This driver was launched in April, I don't think this new version is not compatible with the latest security standards.

I have regularly signed PDFs in the past using Active Client, and recently I started getting the same error and error code using version 2015.016.20039 of Adobe Acrobat Reader DC on Windows 8.1 Pro. I hope this gets fixed soon.

I also have the same issue - Acrobat DC / WIN 7 PRO. I can sign in Reader. It is a new smartcard and I was signing documents with the old card. I can sign documents on other computers and can log in to sites with this one. Seems to be Acrobat DC related. Talked with Adobe support Rep on phone but he was ABSOLUTELY NO HELP AT ALL!!

With the Reader DC release 15.016.20039, we have deprecated use of SHA1 hash while signing. SHA256 has been the default hashing algorithm, but in the prior releases in case the CSP driver doesn’t support SHA256 or higher hashes Reader used to silently fallback to SHA1 hash while creating the signature. In this release, we have removed the silent fallback to SHA1 due to which this error pops up and subsequently signing fails.

Please let me know the driver of the e-token device your are using for signing.

Also, check with the driver manufacturer for the updated driver that should resolve this error.

As you can observe from the above comments, the vast majority is using the SafeNet Authentication Client (8.2) driver.

We have started to use the latest available driver provided by Gemalto in April (SafeNet Authentication Client , version 10.0.43.0) and it still returns the error from the subject in Adobe DC, above mentioned version.

I understand that you didn't permit the fallback to SHA1 any more, but there are other applications which are using the same configuration, calculates the algorithm with SHA256 and doesn't return any error message regarding with the keyset from the token.

While we investigate it further, the workaround provided in the article should help.

"Check with your signature device or driver manufacturer for an updated driver that may resolve this error.

If the requested hashing algorithm is not supported by the signature device, then the solution is to set registry key aSignHash to SHA1 as described on this page - http://www.adobe.com/devnet-docs/acrobatetk/tools/PrefRef/Windows/Security.html#Signing:Ha shAlgorithm. However, this is not a recommended approach as this would set SHA1 as the default hashing algorithm for all signatures, which is considered deprecated industry wide. Therefore, Adobe strongly recommends checking with your signature device or driver manufacturer to get a newer device or driver that supports SHA256 or higher hashes."

We have released a patch today that fixes the Digital Certificates issue that was recently introduced. If you are not already updated to the latest patch, simply open Acrobat and visit Help > Check for updates to apply this patch.