guides:legacy_installation_guide

Workstation Installation Guide

Introduction

With the implementation of the CeRTNA Documentation Wiki, this version of the Workstation Installation Guide serves as consolidation of multiple user guides. This document covers the installation and configuration requirements for the following platforms:

  • APEX Transport Client
  • ERDS Web Client
  • G2G Web Client
  • Entrust PKI Certificates

You can quickly move to any section by clicking the table of contents shown above

Overview

The CeRTNA ERDS workstation configuration requirements are driven by several factors as shown below:

  • Workstation Security As Outlined By The California DOJ
  • Encryption & Authentication Technologies Used By Entrust
  • Two-Factor Authentication Via SafeNet USB Tokens
  • Support Of The ERDS Web Based Application

In order to access the CeRTNA application, an ERDS application must meet the security requirements as outlined by the California DOJ. The California DOJ Baseline Security Requirements can be viewed at the following URL:

https://oag.ca.gov/sites/all/files/agweb/pdfs/erds1/Baseline_9_2014.pdf

Section 4.2.7 of the referenced DOJ document outlines the security requirements for a workstation.

To ensure compliance with the DOJ regulations, a CeRTNA ERDS workstation must pass a security audit before it can be used to process production level electronic recording. A new section has been added to this document that outlines the steps to be taken to prepare for the initial workstation security audit.

The CeRTNA application currently uses a toolkit provided by Entrust to perform authentication and encryption services. The Entrust services make use of Public Key Infrastructure (PKI) and Microsoft Cryptography API (CAPI) technologies. The Entrust toolkit uses Java to deliver its functionality and therefore a CeRTNA ERDS workstation must have a version of Java that is compatible with the version of Entrust tools that are in used by CeRTNA.

To support Two-Factor Authentication the CeRTNA application uses USB token technology provided by SafeNet. Drivers are required to communicate with the token and CeRTNA receives SafeNet drivers from Entrusthat that are compatible with the Entrust toolkit. Information about where to obtain the latest drivers and how to install them is provided later in this document.

Finally, the CeRTNA ERDS application is a web-based .NET application that is served up from a Microsoft Internet Information Services (IIS) web server platform. This means a web browser is required to access the CeRTNA ERDS application functionality. Currently the ERDS application will only work with the Microsoft’s Internet Explorer web browser.

HW & OS Requirements

Hardware and software has changed significantly since CeRTNA's original launch in 2008. Since that time the CeRTNA ERDS application environment is transitioning from a simple web client application to a more sophisticated thick client application named APEX.

Hardware Requirements

The following workstation specifications are designed to satisfy the requirements for running APEX and are current as of May 10, 2025:

  • Processor: Intel i5 or greater
  • Memory: 16 GB Minimum / 32 GB Recommended
  • Disk Storage: 100 GB Recommended (Depends on your environment. See note.)
  • USB Port: Available USB 2.0 port (See note.)
  • Network Adapter: 100 Mbps or higher.

Notes:

  • The SafeNet eToken requires a USB 2.0 or 3.0 style port. USB-C adapters are not supported.
  • CeRTNA exchanges files with the recording vendor software using a Windows folder. This folder can be either a local folder on the local hard drive of the workstation, for example the C: drive, or it can be a shared network folder, for example \\your_server\shared_folder\. If you use a network share, the CeRTNA ERDS workstation will need to have network access to the shared folder or UNC path where the CeRTNA ERDS XML transactions will be accessed for submissions, stored upon retrieval, and or picked up for return. Please refer to the section Folder Structure in the Workstation Installation Guide for a description of how the standard CeRTNA ERDS folder structure should be created.
  • In most cases, the Disk Storage requirements for CeRTNA are minimal. The XML files that are submitted by an agent or returned by a county are moved to a PROCESSED subfolder and APEX automatically keeps the subfolder cleaned up based on a “Number of days to keep files” setting in CeRTNA's agent and/or county configuration record. The current default setting for the “Number of days to keep files” is 45. The larger that number is, the more storage space that will be used. Allocating 100 GB of storage space will most likely cover any storage requirements needed by APEX.
  • If you will be using a standalone workstation, you will need a security cabinet for your ERDS workstation. You can click this link to see a security cabinet that CeRTNA recommends.
  • If you will be submitting transactions, you may need to acquire a scanner and scanning software. The brand of scanner/software is left up to the submitter, however, any scanner/software selected needs to be able to produce, black & white, CCITT T.6 (Group4-Compressed), 300 dpi, TIFF image files.

Operating System Requirements

CeRTNA will certify and support the CeRTNA ERDS software (APEX) and the required tools on the following Microsoft Windows platforms:

  • Windows 10 Professional (32-bit or 64-bit versions.)
  • Windows 11 Professional (64-bit version.)
  • Windows Server 2012 Standard/Enterprise (Installed as a VM.)
  • Windows Server 2019 Standard/Enterprise (Installed as a VM.)

Important: Home Editions of Microsoft Windows operating systems are not supported because they do now have support for Local Security Policy.

Firewall Considerations

APEX communicates using SSL port 443 (https) and some communications take place using port 80 (http). The following table contains a list of hosts that must be reachable in order for APEX to be installed or be used after the installation:

Host IP Address Description
dev-ws02.certna.org 204.246.133.236 APEX installation
apex-setup.certna.org 204.246.133.236 APEX installation
apex-prd.certna.org 204.246.133.237 APEX production ERDS web
apex-prd.certnag2g.org 209.170.199.196 APEX production G2G web
reports.certna.org 204.246.133.238 APEX production ERDS reports
reports.certnag2g.org 209.170.199.202 APEX production G2G reports
*.digicert.com * PKI certificates (Note 2)
*.ssl.com * Code Signing certificate (Note 2)
*.godaddy.com * SSL certificates (Note 2)

CeRTNA no longer interfaces with Entrust, therefore, the references to *.entrust.com and *.entrust.net shown above have been stricken out.

Note 1: CeRTNA recognizes that different firewalls are in service at our customers and that firewall features functions can vary broadly. CeRTNA prefers to minimize the amount of IT administrative support required by creating rules based on the following tolerance and/or capabilities of your firewall:

  1. Use wildcard domains if possible. (Ex: *.certna.org or *.certnag2g.org)
  2. Use host names if possible. (Ex: apex-prd.certna.org or reports.certna.org)
  3. Last resort, use IP addresses.

The preceding list is sorted in order of preference.

Note 2: Several digital certificates are used in support of CeRTNA/APEX, these include SSL certificates, PKI certificates for digital signatures, PKI certificates for encryption/decryption, and code-signing certificates. The CeRTNA APEX application uses core WCF & .NET functionality to verify that the PKI certifcates are still valid and have not expired. Further, during the APEX installation/update process, the code-signing certificate is validated. The lower level WCF & .NET API's communicate using port 80 for OCSP and CRL certificate validation functions. It is important that your firewall team take this into consideration.

Workstation Support

In addition to the locations listed above, there are some additional hosts that you also want to allow in order to facilitate the retrieval of Windows Updates and for CeRTNA remote support.

Host IP Address Description
*.microsoft.com * Top-level Microsoft domain, to avoid issues with Windows functionality. (Note 3)
*.update.microsoft.com * General Windows update domain.

Configuring the firewall rules for Windows Updates and other fundamental OS support, for example, virus definition files for Endpoint Protection or other 3rd party system management tools is the responsibility of your organizations IT staff. The information provided in the preceding table is here simply point out that there are additional URL's that may need to be accommodated beyond those that are required for APEX and/or CeRTNA functionality.

Note 3: Support for Teams meetings and screensharing is also required for remote support of the APEX software.

Supporting Software Requirements

Java Runtime Environment (JRE)

CeRTNA is actively transitioning customers to its APEX software. Although APEX does not require Java, CeRTNA still supports customers using the ERDS or G2G web client to send and retrieve XML transactions. In order to use the CeRTNA ERDS or G2G web client, customers must have a Java Runtime Environment (JRE) installed.

As mentioned in the overview section there are a variety of tools required to deliver the CeRTNA application functionality. An extensive number of hours have been invested by CeRTNA to validate the proper application functionality across operating systems, encryption decryption tools, browsers, platforms (ERDS & G2G), certificate renewals/downloads, application roles (submitters, counties, administrators) etc.

In order for everything to work properly together the most important item becomes the Java Runtime Environment (JRE). Comprehensive functionality will only be supported if you are using one of the following JRE versions:

Due to requirements for installing and/or updating Entrust PKI certificates, CeRTNA cannot support JRE 6 Update 45. If you are still running JRE 6 Update 45, please update your workstation to use one of the supported versions shown in the preceding table. CeRTNA recommends using JRE 8.121, if possible.

Once you have downloaded one of the JRE installation files shown above, unzip the file to a working folder such as C:\JRE_Setup or a folder name of your choosing. Once the zip file has been extracted open the following subfolder: C:\{your workfolder}\ and double-click the JRE setup program to start the setup process. If you are prompted by User Access Control (UAC) to allow the installation, click the Yes button.

Click on one of the following links to view the installation instructions for either JRE7 or JRE8

JRE Version 7 Update 51 Installation Instructions

JRE Version 8 Update 121 Installation Instructions

XML Parser

Starting with Windows 7, support for Microsoft’s Core XML Parser is delivered with the operating system. It does not need to be downloaded and installed separately.

CeRTNA ERDS & G2G web applications require that you set your Internet Explorer browser into Compatibility Mode. If you do not configure your Internet Explorer browser for compatibility mode, you see the message XML Parser Not Found if you attempt to complete a process that requires the application to parse an XML file, such as submitting a transaction or viewing a transaction.

SafeNet Client/Token Installation

These installation instructions are for the SafeNet Authentication Client 10.8

SafeNet Authentication Client

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 APEX 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 CeRTNA G2G workstation as a backup to your CeRTNA ERDS workstation, you should install the SafeNet Authentication Client on your CeRTNA G2G 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.

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

https://knowledge.digicert.com/general-information/how-to-download-safenet-authentication-client

This zip file is approximately 20 MB in size.

Important Note: If you currently have another version of the SafeNet Authentication Client installed you will need to use the Windows Control Panel to uninstall the older version, before installing an updated version of the SafeNet Authentication Client software.

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

Run the downloaded Installer (E.G. SafeNetAuthenticationClient-x64.msi) to start the setup process.

The following window is displayed:

Click the Next button to continue.

The following window is displayed:

You can leave the 'Use the existing configuration settings' checkbox selected.

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 window is displayed:

Use the default program location for the destination folder.

Click on the Next button to continue.

Click the Typical radio button.

Click the Next button.

The following confirmation window will be displayed:

Click the Install 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.

You will see a new 'S' icon in your taskbar. (Lower right area of your screen.) As shown below. The icon will appear dimmed out, until your SafeNet token is inserted.

Token Installation

To use the CeRTNA APEX application for submitting or retrieving transactions on your ERDS workstation, 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 DigiCert PKI certificate, which is used for digital signing and encryption/decryption functionality.

After you receive your SafeNet token, insert the token into an available USB port on your system. The token will be automatically recognized and linked to the SafeNet driver.

Once the device driver is successfully linked to your SafeNet token, the 'S' icon will appear illuminated as shown in the picture below:

This completes the Token Installation.

Entrust Certificate Installation

The CeRTNA ERDS and G2G web applications and the CeRTNA APEX application use Public Key Infrastructure (PKI) technology to perform user authentication, encryption, and decryption functions. These functions are dependent on PKI certificates that are issued by the Entrust Certification Authority (CA).

The Entrust certificates that are installed on your USB token and your G2G workstations use a 3-tier architecture that is structured as follows:

 Root Certificate
    Intermediate Certificate
       End User Certificate

Most of the CeRTNA End User Certificates have been distributed in the past and as a consequence the Intermediate and Root Certificates are already installed on the end-user workstation so existing certificates and renewed certificates typically have the correct hierarchy in place.

The following paragraphs outline the process for verifying your certificate hierarchy and optionally installing intermediate and root certificates.

Verifying PKI Certificate Installation

The certificates that are installed on your token, depend on a ‘certificate chain’ in order to function properly. You can verify that the certificate chain is valid by completing the following steps with your token inserted in the USB port.

Note: Depending on your local IT security policy, you may need to contact your local IT staff to perform the following steps:

Click the Windows Start button and enter mmc.exe in the Search field.

You should see mmc.exe listed at the top of the results list.

Click mmc.exe and the following window will be displayed:

Note: I have my Actions pane visibility turned off. Your window might contain 3 panes instead of the 2 that these screenshots show.

Select the File / Add-Remove snap in… menu option.

The following window is displayed:

Select Certificates in the left panel and click the Add button.

The following window is displayed:

My user account should be already selected. (If not select it.)

Click the finish button. You will be returned to the following updated window:

The certificate snap-in should be shown in the right pane.

Click the Ok button and the following window will be displayed:

In the left pane, click the carat that appears next to Certificates – Current User

In the left pane, click the carat that appears next to the Personal folder.

Click the Certificates folder.

Your window should look similar to the following:

The certificates in the right pane should reflect your identity.

Double-click either certificate and the following window is displayed:

Click the Certification Path tab and the following window is displayed:

If you do not see a 3-tier certification path, your certificate installation is not complete. The most likely reason is that the Entrust Intermediate and Root certificates were not installed when you inserted the token. To resolve this issue, continue with the next section

If your window shows the proper 3-tier certification path, you are finished with the certificate verification process and you can skip the next section entitled Entrust Intermediate & Root Certificate Installation.

Entrust Intermediate & Root Certificate Installation

Windows supports user-level certificate stores and computer-level certificate stores. If you need to manually install the Entrust Intermediate or Entrust Root certificates on your computer, CeRTNA recommends installing these certificates in the computer-level certificate store.

Depending on your IT security policy your Windows userid may not have access to the computer-level certificate store. If this condition exists, you should install your certificate into the user-level certificates store.

Before you can install the Entrust Intermediate and Entrust Root certificates you will need to download them from the following URL:

https://www.certna.org/ErdsUI/Downloads/Entrust_Token_Root_Intermediate_Certs.zip

Once the zip file has been downloaded, unzip it to a working folder. You will have the following two files in your unzipped work folder:

  • Token_Intermediate.cer
  • Token_Root.cer

These two certificates can be installed in either the user-level certificate store or the computer-level security store. CeRTNA recommends installing the certificates in the computer-level store so that you will not have to repeat this process for each Windows user login on the ERDS workstation.

There are a couple of important notes here:

  • You will need Administrator level access on the CeRTNA ERDS workstation in order to install certificates into the computer-level certificate store. CeRTNA recommends contacting your local IT support to assist with this.
  • Depending on your local IT security policy, your Windows user may not have the appropriate authority to access the computer certificate store. If that is the case, then your local IT support staff can assist you with installing the certificates into the user-level certificate store.

To install the Entrust Intermediate and Entrust Root certificates complete the following steps:

Click the Windows Start button and enter mmc.exe in the Search field.

You should see mmc.exe listed at the top of the results list.

Click mmc.exe and the following window will be displayed:

Select the File / Add-Remove snap in… menu option.

The following window is displayed:

Select Certificates in the left panel and click the Add button.

The following window is displayed:

My user account should be already selected. (If not select it.)

Click the finish button. You will be returned to the following updated window:

The certificate snap-in should be shown in the right pane.

Select the Certificates item in the left pane and click the Add button.

The following window is displayed:

Click the Computer account radio button to select it.

Click the Next button. The following window is displayed:

Select Local computer and click the Finish button.

You are returned to the following updated window:

Click the Ok button to be returned to the following window:

I have highlighted the items we are interested in.

Verifying / Installing The Entrust Root Certificate

The first item we are interested in verifying and/or installing is the Entrust Root certificate.

Review the following window:

For each of the two certificate stores (highlighted) you should verify that you do NOT have an entry in the middle pane for ‘Entrust Managed Services Commercial Private Root CA’ (In my sample above, I have already imported my Root certificate.)

If the Trusted Root Certificate is already installed in either of these two certificate stores, you should continue on and verify/install the Intermediate certificate.

If you discover that both the Trusted Root and Intermediate certificates are already installed on your ERDS workstation but you did not see a valid 3-tier certificate path as shown in section Verifying PKI Certificate Installation then this is an indication of a more complex problem and you will need to contact CeRTNA support staff to address the issue.

If the ‘Entrust Managed Services Commercial Private Root CA’ certificate does not exist in the middle pane, you need to install the certificate carefully following steps outlined below:

Right-click click the Certificates subfolder that is shown in the Certificates (Local Computer) / Trusted Root Certification Authorities path (as shown above)

Select All Tasks / Import… from the pop-up menu.

The following window is displayed:

Click the Next button. The following window is displayed:

Click the browse button.

Locate the folder you extracted the zip file into as shown below:

Select the Token_Root.cer file and click the Open button.

The following window is displayed:

Click the Next button.

The following window is displayed:

Click the Next button.

The following window is displayed:

Click the Finish button.

A pop-up window indicating that the certificate was successfully installed should be displayed.

Click the Ok button to close the pop-up window. You will be returned to the Certificates list.

Select the Certificates folder in the Local Computer / Trusted Root Certification Authorities path and you should now have an ‘Entrust Managed Services Commercial Private Root CA’ certificate in the middle pane, as shown below:

The process for verifying and importing the Entrust Intermediate certificates is primarily the same as just completed. The exact steps are documented in the next section.

Verifying / Installing the Entrust Intermediate Certificate

The next item we are interested in verifying and/or installing is the Entrust Intermediate Certification Authority certificate.

Review the following window:

For each of the two certificate stores (highlighted) you should verify that you do NOT have an entry in the middle pane for ‘Commercial Private Sub CA1’ (In my sample above, I have already imported my Intermediate certificate.)

If you discover that both the Trusted Root and Intermediate certificates are already installed on your ERDS workstation but you did not see a valid 3-tier certificate path as shown in the section Verifying PKI Certificate Installation then this is an indication of a more complex problem and you will need to contact CeRTNA support staff to address the issue.

If the ‘Commercial Private Sub CA1’ certificate does not exist in the middle pane, you need to install the certificate carefully following steps outlined below:

Right-click click the Certificates subfolder that is shown in the Certificates (Local Computer) / Intermediate Certification Authority path (as shown above)

Select All Tasks / Import… from the pop-up menu.

The following window is displayed:

Click the Next button. The following window is displayed:

Click the browse button.

Locate the folder you extracted the zip file into as shown below:

Select the Token_Intermediate.cer file and click the Open button.

The following window is displayed:

Click the Next button.

The following window is displayed:

Click the Next button.

The following window is displayed:

Click the Finish button.

A pop-up window indicating that the certificate was successfully installed should be displayed.

Click the Ok button to close the pop-up window. You will be returned to the Certificates list.

Select the Certificates folder in the Local Comptuer / Trusted Root Certification Authorities path and you should now have an ‘Commercial Private Sub CA1’ certificate in the middle pane, as shown below:

Once you have completed this process, you can return to the section Verifying PKI Certificate Installation and re-verify that your three-tier cerification path is displaying correctly. If the three-tier path is still not displaying correctly, you will need to contact CeRTNA support for additional assistance.

Revisions

Date Version Name Description
05-21-2009 1.0 Brett Zamora Initial draft.
04-29-2011 1.1 Brett Zamora Added updates based on knowledge gained during first year of operation. These include adjusting settings on the Java Runtime Environment and some additional FAQ’s.
05-10-2011 1.2 Brett Zamora Updated graphic and text placement.
08-10-2015 2.0 Brett Zamora Reworked look & feel of this document and updated content to reflect a more current set of software. Also added section about preparing the workstation for the initial security audit.
04-06-2016 2.1 Brett Zamora (1) Added version to the cover page. (2) Removed reference to Internet Explorer 8. The only officially supported browser is Internet Explorer 11. (3) Updated Java Runtime section to provide information about support for JRE 8. (4) Updated the SafeNet Token installation section to include a comment regarding uninstalling existing SafeNet 7.x software and also updated the section heading to point out that the section only applies to ERDS platforms, not G2G platforms. (5) Updated Table Of Contents.
07-27-2017 3.0 Brett Zamora (1) Converted Workstation Installation Guide to a wiki format. Versioning will now be managed via wiki engine. (2) Updated content so that this single document contains the installation requirements for the ERDS, G2G, and APEX platforms.
guides/legacy_installation_guide.txt · Last modified: by brett.zamora