When attempting to create a Digital ID for digital signatures in Adobe Reader on Mac OS, Adobe Reader does not detect the inserted Safenet hardware token containing the certificate to be used.
If the Safenet token is inserted and detected by other software, such as the Safenet Authentication Client application, the PKCS11 module for the Safenet token needs to be added to Adobe Reader manually for it to detect the token for use as a Digital ID.
- Within Adobe Reader, navigate to the Preferences Menu, and select Signatures from the Categories listed on the left.
- Next to Identities & Trusted Certificates, click More.
- Under the Digital IDs list on the left, select PKCS#11 Modules and Tokens.
- Select Attach Module.
- Enter the path to the LibeTPkcs11.dylib module, which was installed by the Safenet Authentication Client during its installation (in usr/local/lib/LibeTPkcs11.dylib by default), and select OK.
- If the module loaded successfully, the Safenet token should now be listed under the PKCS#11 modules and tokens section, and the token can be logged into using the Safenet Client credentials.
This process will allow the certificates on the Safenet token to be used when creating a new Digital ID for digital signatures.