2016-04-30 04:39:32 +00:00
|
|
|
|
2016-04-21 14:26:04 +00:00
|
|
|
=== System Requirements
|
2016-04-20 21:49:18 +00:00
|
|
|
|
2017-08-28 12:50:14 +00:00
|
|
|
These are the requirements to run the {project_name} authentication server:
|
2016-04-20 21:49:18 +00:00
|
|
|
|
|
|
|
|
* Can run on any operating system that runs Java
|
|
|
|
|
* Java 8 JDK
|
|
|
|
|
* zip or gzip and tar
|
|
|
|
|
* At least 512M of RAM
|
|
|
|
|
* At least 1G of diskspace
|
2018-01-26 14:52:39 +00:00
|
|
|
* A shared external database like PostgreSQL, MySQL, Oracle, etc. {project_name} requires an external shared
|
2017-08-28 12:50:14 +00:00
|
|
|
database if you want to run in a cluster. Please see the <<_database,database configuration>> section of this guide for more information.
|
|
|
|
|
* Network multicast support on your machine if you want to run in a cluster. {project_name} can
|
2016-04-29 16:09:09 +00:00
|
|
|
be clustered without multicast, but this requires a bunch of configuration changes. Please see
|
2017-08-28 12:50:14 +00:00
|
|
|
the <<_clustering,clustering>> section of this guide for more information.
|
|
|
|
|
* On Linux, it is recommended to use `/dev/urandom` as a source of random data to prevent {project_name} hanging due to lack of available
|
2016-12-19 13:25:51 +00:00
|
|
|
entropy, unless `/dev/random` usage is mandated by your security policy. To achieve that on Oracle JDK 8 and OpenJDK 8, set the `java.security.egd`
|
|
|
|
|
system property on startup to `file:/dev/urandom`.
|
