- Description
- Setup - The basics of getting started with ejbca
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
This module installs. configures, and (partly) manages an EJBCA installation. EJBCA is an open-source Certificate Authority.
The module manages both the installation and configuration EJBCA, and provides a custom type that allows for managing end entities, using the SOAP API.
EJBCA runs on a JEE5 compliant Java application server (see https://www.ejbca.org/docs/Application_Servers.html). This module uses the biemond/wildfly module, which limits the choice to JBoss or Wildfly.
EJBCA stores its data in a database (see the file conf/database.properties.sample from the distribution for a list). This module can handle installation of the database driver, but does not manage the database.
Previous versions of EJBCA required an instance with 2 CPUs. I can't find that requirement anymore, so I'm not sure it still holds. However, if you're having trouble installing EJBCA using this module, consider trying installing it on a bigger instances, with (at least) 2 CPUs.
A Java version that's compatible with EJBCA's version has to be installed before EJBCA can be installed.
Minimal usage:
include ejbcaThis installs the current open-source version of EJBCA with the default configuration:
- database: H2
- organization: 'EJBCA Sample'
- country: 'SE'
This module does not manage the database.
See REFERENCE.
In general, if you want to change a setting, it's best to start over entirely. Also, this module does not support automatic upgrading from one database to another, or from one application server to another, or to a newer version of EJBCA.
This module had only been tested on Ubuntu 16.04 and 18.04.