Before beginning this article, it is necessary that you have successfully completed the article Install and Configure S-Series on First Use.
This article will describe how to configure the vSEC:CMS in order to manage the lifecycle of the Safenet eToken 5100 and 5110 smart card tokens as these tokens have unique behavior to other smart card tokens in the Safenet minidriver suite. In this use-case we will configure the smart card token to be issued with a Windows smart card logon certificate.
Note: The PKI used in this example use case will be an MS CA.
Important: If managing eToken 5100 or 5110 FIPS enabled tokens the host from which you are managing these tokens will need to have SAC installed on it as the SAC PKCS#11 library is used to initialize these tokens when registering them with vSEC:CMS.
Important: The eToken minidriver needs to be installed on any host where you will be managing these tokens from. It is recommended to use version 9.0.54 (or later) of the eToken minidriver. You can ascertain the version number from C:\Windows\System32, right click the file eTokenMD.dll and from Properties – Details you can see the version number.
Important: It is required that you are running version 5.6.1 or later of the vSEC:CMS.
Step 1 – Configure Smart Card Access
1. From Options – Smart Cards attach the eToken that you will manage with the vSEC:CMS. The vSEC:CMS will filter the card type and present the card template..
2. If one or more entries are filtered then select an entry and click the Delete and continue to delete entries if more than one is filtered and shown.
3. Click the Add button and in the dialog that pops up click Add again and click Get from the dialog that pops up and click Ok. Click Save to save and close the configuration with all default settings configured. It is not normally recommended to edit the default settings shown.
Step 2 – Configure Smart Card Template
1. From Templates – Card Templates click the Add
2. Click the Edit link beside General.
3. Enter a template name and attach an eToken 5110 smart card that is to be managed by this template and click the Detect You should see information in the window showing that a SafeNet eToken is detected. Click Ok to close out of the dialog.
4. Accept all default settings in the General dialog and click Ok to save the settings and close this dialog.
5. Click the Edit link for Issue Card.
6. From User ID Options section enable Assign User ID and select the AD connection already configured.
From Enroll Certificate Options section enable Enroll certificate(s) and click the Add button. Select the CA connection already configured from the Certificate Authority drop down list and select the smart card logon certificate template as configured on your CA from the Certificate template list.
Accept all other defaults for the Issue Card dialog and click Ok to save and close.
7. Click Ok to save and close the template.
Important: It is important that the Windows smart card logon certificate template on the CA is configured to require an authorized signature. From the Issuance Requirements tab for the certificate template properties on the CA make sure to enable This number of authorized signatures and set a value of 1 and for Application policy drop down list select the Certificate Request Agent option.
Step 3 – Issue Smart Card Token
1. From the Lifecycle page attach the smart card token that is to be issued and click the Issued Select the card template from the Select card template drop-down list and click the Execute button.
2. Enter the Operator token PIN (Passcode) code when prompted.
3. Select a user from AD that the smart card token is to be issued to.
4. When the issuance completes a message dialog indicating that an authentication key has been added to the vSEC:CMS will appear followed by a short summary dialog with details on what operations have been performed.
The smart card token is now in an Issued state as can be seen from the process diagram. By default, the smart card PIN will be blocked so it will be necessary to unblock the smart card. Typically, the person who will use this smart card will set the PIN code on the smart card.
5. Click the Active oval and click the Execute button.
6. Enter the Operator token PIN (Passcode) code when prompted.
7. Enter the PIN code that will be set on the smart card token. Click Initiate to set the PIN code on the smart card and make it active.
8. A summary dialog will appear. Click Ok to close.
9. The smart card will now be in an active state and can be used to perform Windows Smart Card logon.
Important: It is possible to configure a PIN policy from Template – PIN Policies for the non-FIPS enabled eTokens by selecting Safenet eToken cards. This can then be configured to be applied in the card template.
For the FIPS enabled eTokens the supported PIN policies that can be set on these tokens using the vSEC:CMS allow the following policies:
- Alpha upper case + alpha lower case + numeric + special characters
- Alpha lower case + numeric + special characters
- Alpha upper case + numeric + special characters
- Alpha upper case + alpha lower case + numeric
- Alpha upper case + alpha lower case + special characters
Step 4 – Perform Windows Smart Card Logon
On a Windows system connected to the domain attach the smart card token and enter the smart card PIN code created earlier to logon.
This completes the use case.