Electronic signature in Adobe error pksc#11

[pitbull03]

I have a problem signing a document in Adobe using a qualified signature, error pkcs#11 is displayed. I removed and added the module again but no change. Where is the problem? This signature worked before.

[Tariq Ahmad]

Hi 

Sorry for the troubled experience, based on my findings on the error code:

Error 0x1011 typically indicates that the token or certificate is not accessible, which can be due to:

• Token not inserted properly

• Smart card reader not detected

• Token middleware (PKCS#11 driver) not installed or not recognized

• Incorrect configuration in Acrobat’s Digital ID and Trusted Certificates settings

• Outdated token drivers or conflicts with other cryptographic software

You may try the following and let us know how it works:

· Ensure the Token/Smart Card Is Properly Inserted:

o   Check that the USB token or smart card is fully connected and detected by your OS.

·  Restart Acrobat & Reconnect Token:

o   Close Acrobat, unplug/replug the token, and reopen Acrobat to retry.

·  Check PKCS#11 Module Configuration in Acrobat:

o   Go to:

§  Edit > Preferences > Signatures > Identities & Trusted Certificates > More...

§  Under PKCS#11 Modules and Tokens, make sure the correct module is added and enabled.

·  Update Middleware/Drivers:

o   Download the latest drivers or middleware for your token (e.g., eToken, SafeNet, Gemalto) from the manufacturer’s website.

·  Re-add Digital ID:

o   Remove and re-import the Digital ID if corrupted:

§  In Acrobat: Edit > Preferences > Signatures > Digital IDs

·  Try with Another USB Port or Machine:

o   Eliminate hardware-specific issues by testing on a different system or USB port.

·  Check Token Lockout:

o   Repeated incorrect PIN entries may lock the token. Use the token’s management utility to verify lock status.

~Tariq

[ls_rbls]

++Adding to the topic

Hi @pitbull03 , 

Is this occurring on a macOS computer? It is not clear if you are referring to employing a self-signed certificate-based digital signature or using a smart card with a reader.

Please describe in a little more detail the workflow that you were trying to achive.

[pitbull03]

I work on Mac. This is a cloud signature. It works on the /usr/local/lib/libencardp11.dylib library. The signature worked in Adobe but suddenly stopped. I reinstalled Adobe, reinstalled the signing software, removed the module, added it again. The signature works fine through the signing software.

[ls_rbls]

@pitbull03 ,

If you are using a Cloud certificate-based Digital ID,  it is possible  that the RootCA (Root Certification Authority) is not trusting your certificate-based Digital ID in the certificate's trust chain.

I suspect that this falls on Bullet #4 , of the guidance posted by @Tariq Ahmad :

Incorrect configuration in Acrobat’s Digital ID and Trusted Certificates settings

Sometimes, this happens after an unattended update takes place or a major upgrade from an older version of the operating system to a newer version, which directly impact the System's Key Chain.

See that explained in more context here:

https://apple.stackexchange.com/questions/422332/how-do-i-update-my-root-certificates-on-an-older-ve...

https://discussions.apple.com/thread/255764636?sortBy=rank

https://support.apple.com/en-ca/103252

https://support.apple.com/en-us/103272

https://it-training.apple.com/tutorials/deployment/dm040/

Can you confirm that this behavior started happening after a recent update of your macOS?

Are you also able to verify if you can see or locate where are your root certificates using Keychain Access?

On Acrobat, You can also check if manually updating the Adobe Approved Trust List (AATL) can resolve this issue:

https://helpx.adobe.com/acrobat/kb/approved-trust-list-update-dialog.html