Fix Acrobat RSA Smart-Card Signing Errors with EC Certificate Chains on macOS
Question details
Resolve an Acrobat Reader signing error involving an RSA smart-card key and a certificate issued by an EC certificate authority.

- Product
- Adobe Acrobat Reader
- Device & OS
- macOS
- Scenario
- The user wants to digitally sign a PDF with an RSA private key stored on a smart card, using a certificate whose issuer uses an EC key.
- Observed behavior
- Signing may fail if Acrobat or CryptoTokenKit selects the certificate-chain signature algorithm instead of the certificate's private-key algorithm.
Have the smart card, its PIN, and the token vendor's macOS middleware available. Check which Acrobat version and token plugin you are using, and obtain a public copy of the signing certificate if you need to inspect it.
Verify the RSA Certificate and Smart-Card Key
Confirm that the selected certificate and the card's private key match before troubleshooting the signing provider.
Open Keychain Access, locate the signing certificate, and inspect its details. Alternatively, run `openssl x509 -in certificate.pem -noout -text` in Terminal and check that the public-key algorithm is RSA.
In the certificate details, look for the certificate signature algorithm. An ECDSA signature can indicate that an EC issuer signed the certificate; it does not mean the certificate's own public key is EC.
Open the smart-card vendor's management utility and check that the selected certificate is associated with the matching RSA private key. Ask the vendor how to verify the association if the utility does not show it.
Open the PDF in Acrobat Reader, choose All tools > Use a certificate > Digitally sign, and select the verified certificate. Enter the card PIN when prompted.

Test the Token's PKCS#11 Module
Try the token vendor's PKCS#11 module as an alternative to the CryptoTokenKit path when supported.
Update the Software and Report a Provider-Specific Failure
Use this approach when the same smart-card certificate signs successfully elsewhere but fails in Acrobat.
Work with PDFs and Office Files in WPS Office
WPS Office is a free, lightweight alternative for viewing and editing common office files in a familiar interface. Its format compatibility makes it easy to move existing documents into your workflow, though it does not fix Acrobat or CryptoTokenKit smart-card signing errors.

Frequently Asked Questions
Can an RSA certificate be issued by an EC certificate authority?
Yes. The certificate can contain an RSA public key while its issuer signs it using ECDSA. Check the public-key and certificate-signature algorithms separately in Keychain Access or with `openssl x509 -in certificate.pem -noout -text`.
Does a certificate's ECDSA signature mean my smart-card key is EC?
No. The certificate-signature algorithm identifies how the issuer signed the certificate. Check the certificate's public-key algorithm and the card vendor's utility to identify the user's key.
How do I try PKCS#11 instead of CryptoTokenKit?
Obtain the macOS PKCS#11 module from your token vendor. In Acrobat Reader, check Preferences > Signatures > Identities & Trusted Certificates for security-module settings and add the module if your version supports it.
What should I send Adobe or the token vendor if signing still fails?
Provide the Acrobat and macOS versions, token and middleware versions, certificate-chain algorithms, the error message, and results from Acrobat and another signing application. Do not share your PIN or private key.




