Pre-Installation Steps

Prerequisites

You must have installed the operating system on the server that will host the Validation Authority software.
The Validation Authority installer requires Java to be set in the execution path. This is required only to run the installer. After the Validation Authority installation has been completed, Validation Authority will work fine, even if the Java executable is not set in the system's execution path.
To install Validation Authority on Windows/Linux, Java Development Kit OpenJDK 11.0.2/15.0.2 (from OpenJDK.org) or Oracle JDK 11.0.12/15.0.2 is required.

Important: To use OpenJDK/Oracle JDK 17.0.2 as JVM, you need OpenJDK 11.0.2/15.0.2 or Oracle JDK 8/11.0.12/15.0.2 to launch the installer.

Note: JAVA_HOME & PATH variables are to be set in system environment variables for the installer to work.

Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files should be installed if planning to configure Validation Authority with larger key sizes (AES with key sizes larger than 128-bit).

Install Key Storage System

Validation Authority maintains a small number of secrets and private keys used to protect sensitive data and sign OCSP responses. These keys are protected using either the provided software-based protection keystore or a Hardware Security Module (HSM) from a supported third-party vendor.

If you plan to use an HSM in your configuration, then install and configure it according to the manufacturer instructions before you install Validation Authority.

During Validation Authority configuration, you will be asked the type of key storage system you will be using with Validation Authority.
For detailed information on using a Thales Luna HSM, see Thales Luna Specific Information.
For detailed information on using an AEP Networks Keyper HSM, see AEP Keyper Specific Information.
For detailed information on using a Entrust nShield HSM, see Entrust nShield Specific Information.

Install Database

Validation Authority stores certificate and revocation information in a relational database.

Production installations require the separate installation and configuration of a full-featured Structured Query Language (SQL) database (such as Oracle®, Microsoft® SQL Server, or PostgreSQL®).

Note: If you plan to use a separate database for your configuration, you must install and configure it according to the manufacturer instructions before you install Validation Authority. During Validation Authority configuration, you will be prompted for the database to be used with Validation Authority. You must have a user account to connect to the database.