| Java |
|---|
| OpenJDK 11 | Recommended for running SignServer. Ensure that you are using an application server which supports Java 11, for example, WildFly 14+. |
| OpenJDK 8 | Deprecated: Support for this version will be dropped in an upcoming release. |
Oracle Java 8 | Deprecated: Support for this version will be dropped in an upcoming release. Note that if using Oracle Java, you must enable the unlimited policy files, see Install Java. |
| Application Server |
|---|
| WildFly 24 | For instructions on how to set up your application server, see Application Server Setup. |
| JBoss EAP 7.4 | For instructions on how to set up your application server, see Application Server Setup. |
| JBoss EAP 7.0-7.2 | Deprecated: Support for these versions will be dropped in an upcoming release. For instructions on how to set up your application server, see Application Server Setup. |
| WildFly 9, 10, 11, 14 | Deprecated: Support for these versions will be dropped in an upcoming release. For instructions on how to set up your application server, see Application Server Setup. |
| Database |
|---|
| MariaDB 5.5/10 | Recommended. |
MySQL 5.5 |
|
| PostgreSQL 9 |
|
| Oracle Database 10/11g |
|
| NoDB | You can choose to install SignServer without a database management system and instead rely on SignServer to manage persistence using local files, see SignServer without Database. |
| Deployment Tool |
|---|
| Apache Ant 1.9.1 or later |
|
| Optional: Build Tool |
|---|
| Apache Maven 3 | Only required when building SignServer from source. |
| Optional: Locale |
|
|---|
| UTF-8 | Ensures that the file name is properly sent back from SignServer even with special characters. |