SSH.COM PrivX Documentation Hub

Welcome to the SSH.COM PrivX documentation! Here you'll find the PrivX administration manual, use case specific guides as well as API specifications.

Documentation    API Reference

Quick Server Setup



This article describes setting up PrivX for quick evaluation purposes. If you are setting up PrivX for production, refer to Deployment Overview instead.

For evaluation purposes, set up one PrivX server on a fresh CentOS/Red Hat 7 or 8 machine as follows:

To set up a PrivX server:

  1. Add the EPEL and PrivX repositories for downloading PrivX packages and dependencies:

    • On CentOS/Red Hat 7:

      yum update
      yum install
      yum install epel-release
      rpm --import
      curl -o /etc/yum.repos.d/ssh-products.repo
    • On CentOS/Red Hat 8:

      yum update
      yum install
      yum install epel-release
      rpm --import
      curl -o /etc/yum.repos.d/ssh-products.repo
  2. Install the latest PrivX packages with:

    yum install PrivX
  3. Configure PrivX with:


    The following lists the required information, along with some recommended values for evaluation setups:

    • PKCS #11-keyvault settings: N
    • NTP server address:
    • FQDN and IP address(es) of the server. You can obtain these by opening another terminal and running hostname --fqdn and ip addr respectively.
    • Local or external database: L
    • Database name and credentials. You can go with the defaults.
    • Credentials for the initial superuser account.

    Once the postinstall finishes, the PrivX server is operational.

  4. License your PrivX server to enable its features:

    Open a browser and navigate to the FQDN or IP address of your PrivX server. Log in with the superuser credentials provided earlier.

    In the PrivX GUI, go to Administration‚ÜíLicense and enter your license code.

    You have now set up a PrivX server for evaluation purposes.

Updated 6 days ago

Quick Server Setup

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.