System Requirements
HW Requirements
You don’t need much more than your Java container of choice requests for the PowerAuth deployment. We suggest following minimal configuration:
- 2x CPU 2.5GHz
- minimum available RAM: 4GB
- sufficient disk space for log storage: 10GB
There are two ways to deploy PowerAuth Server:
- Java container
- Docker
Running PowerAuth server from console using the java -jar command is not supported.
Supported Java Runtime Versions
The following Java runtime versions are supported:
- Java 17 (LTS release)
Powerauth Server may run on other Java versions, however we do not perform extensive testing with non-LTS releases.
Deployment in Java Container
PowerAuth Server primary installation method is running the WAR package in the Java VM environment. This chapter provides detailed system requirements.
It is suggested to deploy PowerAuth in its own Java Servlet Container. PowerAuth Server is currently tested with following container technologies supporting Jakarta EE 9:
- Apache Tomcat 10.x or newer
- Wildfly 23 or newer
- JBoss EAP 8 or newer
PowerAuth supports any JPA2 compatible database, and it is tested with:
- Oracle Database 11g, 12c, 19c, or 21c or
- PostgreSQL 9.5.4 or newer, or
Note that MSSQL database is not supported due to unreliable row locking.
When deploying the PowerAuth Server, please follow the specifics of your application server.
Deployment is described in details in a separate documentation:
Deployment in Docker
You can also deploy PowerAuth Server in Docker. This is especially convenient for development.
You need following software versions:
- Docker 17.3.1 or newer, and
- Docker Compose 1.11.2 or newer, and
- Unix-based operating system, preferably macOS, or any stable Linux distribution
Deployment is described in a separate documentation:
Entropy
The PowerAuth stack requires significant amount of entropy because of random number generators (RNG) used for cryptography. When not enough entropy is available, the whole system may dramatically slow down or even get stuck. That may happen especially in virtualized environment.
For Linux Kernel lower than 5.4, the minimal required entropy is 256, ideally more than 1024. For Linux Kernel 5.4 and higher: the minimal required entropy is 256 (it does not report more anyway).
Command to get available entropy bits:
cat /proc/sys/kernel/random/entropy_avail
We recommend using Linux Kernel 5.4 and newer, where /dev/random does not block anymore.
If you must run an older version, consider another source of entropy such as haveged.