-
Notifications
You must be signed in to change notification settings - Fork 709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using OpenSC enabled token for signing PDF documents in Adobe #3104
Comments
There is an outstanding issue with epass2003 FIPS version. #2843 that may be related. Can you run this command from #2834 to reat the ATR and a data object with flags:
If it looks like #2843 (comment) it is one of the tokens with the problem. Feitian has been slow to respond to the bug reports. Please submit a bug report if you nave one of these. Last know updates which appear to be from Feitian are from: @haijie-ftsafe and @xaqfan To answer your question, Windows when it sees a smartcard will add add a certificate to the cert store when it sees a smartcard with info on which card it came from. This may be long term or just while the card is inserted. Some commands you can use are |
I am also looking for the same, I wonder how Adobe/Windows recognizes the certificate from card and show it in Windows Digital ID? |
Has anyone tried to use epass2003 or entersafe tokens to sign PDF documents via Adobe?
If so, can someone advise how does Adobe know that certain certificates that are stored in the certmanager of Windows need to communicate with a smart card while others don't?
Is there a specific way in which the certificates are stored in the certificate manager of Windows?
The text was updated successfully, but these errors were encountered: