DokuWiki

CeRTNA no longer supports the SafeNet Token Utilities 7.x or the SafeNet Authentication Client 8.3. These instructions are for the SafeNet Authentication Client 10.2

The following items should be taken into consideration before installing the SafeNet Authentication Client:

• If you are using APEX and do not plan to send or retrieve transactions using the CeRTNA ERDS web client you do not need to install the SafeNet Authentication Client.
• If you are using a CeRTNA G2G workstation you do not need to install the SafeNet Authentication Client.
• Important: If you plan to use your APEX or CeRTNA G2G workstation as a backup to the CeRTNA ERDS workstation, you should install the SafeNet Authentication Client on your workstation.

CeRTNA uses SafeNet USB tokens for ‘two-factor authentication’. These tokens require drivers to be installed in order to recognize the token. Currently CeRTNA is supporting two different types of tokens, the SafeNet iKey 4000 token and the SafeNet 5100 eToken (Our newer tokens are branded with Symantec, however, they are still SafeNet 5100 eTokens.)

The current version of the Entrust SafeNet Authentication Client software can be downloaded from the following URL:

https://admin.certna.org/Downloads/SAC102.zip

This zip file is approximately 75 MB in size.

Important Note: If you currently have the SafeNet 7.x or SafeNet 8.3 software installed you will need to uninstall the SafeNet 7.x Client Tools and the SafeNet iKey Drivers or the SafeNet Authentication Client 8.3 before you can install the SafeNet Authentication Client 10.2 software. The SafeNet 7.x or SafeNet 8.3 software can be uninstalled via the Windows Control Panel and you may have to restart your computer when the software is being uninstalled.

To install the SafeNet 10.2 Client software make sure your token is NOT plugged in.

Unzip the SAC102.zip file to a working folder, for example C:\SAC102_Setup or a name of your choosing.

Once the zip file has been extracted open the following subfolder:

C:\{your workfolder}\SafeNet Authentication Client 10.2\EXE Installer

Double-click the SafeNetAuthenticationClient-x32-x64-8.3.exe program to start the setup process.

The following window is displayed:

Click the Next button to continue.

The following window is displayed:

Click the Next button to continue.

The following window is displayed:

Click on the I accept the license agreement radio button.

Click on the Next button to continue.

The following IMPORTANT window is displayed:

IMPORTANT: By default the Standard radio button is selected. (You must change this.)

Click the BSec-compatible radio button.

Note: SafeNet iKey4000 tokens require BSec compatibility and the SafeNet 5100 tokens function with this setting as well.

Click the Next button.

The following confirmation window will be displayed:

Click the Next button to start the installation.

You will see a User Access Control (UAC) prompt requesting permission to install the software. Select Yes to allow the software to be installed.

The following window is displayed while the installation progresses:

When the installation completes, the following window is displayed:

Click the Finish button.

To use the CeRTNA ERDS application for submitting or retrieving transactions customers must complete a fingerprint/background check. Once this process is complete and the approval paperwork has been provided to CeRTNA staff a SafeNet token will be mailed to you. The token will contain your Entrust Authentication certificate and your Entrust Encryption certificate.

After you receive your token, insert your Token Key into an available USB port on your system. The Token will be automatically recognized and installed as shown in the figure below. This occurs because of the SafeNet Authentication Client software/driver installation completed in an earlier step.

Once the device driver software is successfully installed you will see another popup as shown in figure below.

Now you should see a confirmation that your Token has been inserted as shown in the figure below.

This completes the Token Installation.