vastool is a script-friendly command line utility that exposes a wide range of functionality to the Unix/Linux system administrator. Safeguard Authentication Services for Smart Cards adds an additional smartcard command to allow configuration and troubleshooting of smart card-related issues. The following table lists some of the commands and functionality which you can access by running vastool smartcard command. For a complete list, see the vastool man page.
Table 1: vastool smartcard commands
||Configure smart card related settings such as the PKCS#11 driver and PAM.|
||Display information about smart cards and drivers.|
||Test smart card functionality.|
||Manage the store of trusted certificates.|
||Remove smart card related settings.|
PKCS#11 is a standard software interface for accessing cryptographic functions on smart cards. Safeguard Authentication Services for Smart Cards uses the vendor-provided PKCS#11 drivers to interface with the card.
Safeguard Authentication Services integrates with third-party drivers, such as OpenSC. Once the drivers are installed, Safeguard Authentication Services references these drivers from the installed shared library; therefore, you need to know the name and location of this library when you configure Safeguard Authentication Services for Smart Cards.
Note: Safeguard Authentication Services for Smart Cards is derived from the RSA Security Inc. PKCS#11 Cryptographic Token Interface (Cryptoki).
Installing Safeguard Authentication Services for Smart Cards
Before you install the smart card drivers and the Safeguard Authentication Services software, you must first install the Safeguard Authentication Services agent and join your Unix host to the Active Directory domain.
Refer to the Safeguard Authentication Services Installation Guide for step-by-step instructions. See the Authentication Services - Technical Documentation page on the One Identity support site for this guide.
When using Safeguard Authentication Services for Smart Cards, you must install and configure vendor drivers for your cards and readers. For example, you must have a working PKCS#11 library. This is a shared library that implements the PKCS#11 Cryptographic Token Interface Standard. Consult your smart card vendor documentation for more details.