Trial and POC Prerequisite

System Requirements

The Minimum Requirements are meant for trial, sandbox, and POC environments, Recommended Requirements are intended for production deployments.

Minimum requirements for basic deployments and trials

Application Server with PAM Internal Database

4 CPU Cores

8 GB RAM (4GB is serviceable but 8GB is better)

30 GB Disk Space

Base OS: Windows Server 2012 R2 – 2019 Or

Linux Server, Latest LTS version (Centos, RHEL, Amazon Linux, Ubuntu)

Recommended requirements for Production deployments

PAM Application server

External Database Server

4 CPU Cores

Choose one of the following Databases

16 GB RAM

MySQL, MariaDB, MS SQL, PostgreSQL, Oracle, Azure SQL, AWS Aurora, AWS RDS

100 GB Disk Space

Follow the database vendor’s hardware and software requirements

Windows Server 2016 – 2019 Or

Linux Server, latest LTS version (Centos, RHEL, Amazon Linux, Ubuntu)

 

Hardware Requirements

PAM can be installed on a physical server or virtual machine on premise or in the cloud.

If you would like to set up front-end (application) clustering, you will need to have two or more PAM servers (PAM Nodes) available and an external database.

For testing of high availability for the Database Server side, you can use your existing high availability database infrastructure or database mirroring. If you choose to test this, this is something your database team will need to prepare in advance.

Software Requirements

Application Server

PAM can run on Windows or Linux. We recommend installing PAM on freshly installed and updated Windows Server 2016 or newer or a Linux Server OS such as the latest LTS version of Centos, RHEL, Amazon Linux, or Ubuntu.

Database Server

PAM comes with an internal database (Apache Derby) which is fine for POC, Trials and Small deployments that do not require HA.

For additional scalability an external database can be created in an existing database instance, or a new installation of a database server.

PAM supports several different database types including MySQL, MariaDB, MS SQL, PostgreSQL, Oracle, Apache Derby, Azure SQL, AWS Aurora, and AWS RDS.

If you plan on using an external database please have an account with the appropriate permissions available and the database pre-created as per our installation guide.

If using MySQL or MariaDB as your external database, please make sure Pessimistic Locking is enabled. Optimistic locking, which may be the database's default setting, may cause issues with some PAM functionality and is therefore not a supported setting.

Installation Guides

PAM Installation and Setup

Checklist:

  • Windows or Linux Server (1 server, minimum)

  • Application server prerequisites above

  • Use internal database or external Database Server (Pre-created database, 1 instance, minimum)

  • Trusted Third Party Certificate to replace PAM Self Signed Certificate for HTTPS

  • AD or LDAP Credentials if AD/LDAP integration is available or use PAM internal directory services.

  • SMTP and/or IMAP Credentials for email integration (notification and approval)

  • Firewall Ports necessary

  • Advanced implementations and integrations could include various MFA and SSO providers as well as API integrations. If questions remain or issues arise while using PAM, please contact the Support team: https://support.imprivata.com/.

Test Accounts

To test some of the basic features of PAM we recommend you have a few servers and accounts ready.

  • Windows Server to Test RDP and password rotation

  • Linux Server or Linux based Network Device to test SSH sessions and password rotation

  • Native Client Testing using PAM advanced RDP, SSH and Http(s) proxies

  • Additional Test Machines and Test accounts can be added as testing progresses