EJBCA

EJBCA, is a free software public key infrastructure (PKI) certificate authority software package maintained and sponsored by the Swedish for-profit company PrimeKey Solutions AB, which holds the copyright to most of the codebase. The project's source code is available under terms of the Lesser GNU General Public License.

EJBCA
EJBCA 6.5.0 in English – Administration
Developer(s)PrimeKey Solutions AB
Initial releaseDecember 5, 2001 (2001-12-05)
Stable release
7.3.1.2 / March 23, 2020 (2020-03-23)
Repository
Written inJava on Java EE
Operating systemCross-platform
Available inBosnian, Chinese, Czech, English, French, German, Japanese, Portuguese, Swedish, Ukrainian, Vietnamese
TypePKI Software
LicenseLGPL-2.1-or-later
Websitewww.ejbca.org/ 

Design

The system is implemented in Java EE and designed to be platform independent and fully clusterable,[1] to permit a greater degree of scalability than is typical of similar software packages. Multiple instances of EJBCA are run simultaneously, sharing a database containing the current certificate authorities (CAs). This permits each instance of the software to access any CA. The software also supports the use of a hardware security module (HSM), which provides additional security. Larger-scale installations would use multiple instances of EJBCA running on a cluster, a fully distributed database on a separate cluster and a third cluster with HSMs keeping the different CA keys.

EJBCA supports many common PKI architectures[2] such as all in a single server, distributed RAs and external validation authority. An example architecture is illustrated below.

Key features

Multiple CA instances

EJBCA supports running unlimited number of CAs and levels of CAs in a single installation. Build a complete infrastructure, or several, within one instance of EJBCA.

Online Certificate Status Protocol

For certificate validation you have the choice of using X.509 CRLs and OCSP (RFC6960).

Registration authority

The EJBCA software includes a separate registration authority (RA) front end that can run on the same instance as the CA or distributed as external RAs. Communication between the CA and the RA is only using outgoing network connections to insulate the CA from less trusted networks, where the RA is typically placed.

Multiple algorithms

You can use all common, and some uncommon algorithms in your PKI. RSA, ECDSA and DSA, SHA-1 and SHA-2. Compliant with NSA Suite B Cryptography.

Different certificate formats

EJBCA support both X.509v3 certificates and Card Verifiable certificates (CVC BSI TR-03110). Certificates are compliant with all standards such as RFC5280, CA/Browser Forum, eIDAS, ICAO 9303, EAC 2.10 and ISO 18013 Amendment 2 eDL.

PKCS#11 HSMs

Using the standard PKCS 11 API you can use most PKCS#11 compliant HSMs to protect the CAs’ and OCSP responders’ private keys.

Many integration protocols and APIs

EJBCA was designed with integration in mind. Most standard protocols are supported, CMP, SCEP, EST, and ACME as well as web services. Using integration APIs it is possible to integrate EJBCA as a certificate factory, not exposing its native user interfaces.

High performance and capacity

You can build a PKI with capacity of issuing billions of certificates at a rate of several hundreds per second.

gollark: Well, yes.
gollark: I was going to just use my Malbolge to Brain[REDACTED] compiler.
gollark: Yep!
gollark: I agree.
gollark: What good design.

References
  1. "Automated and large scale operations".
  2. "PKI Architectures".

Further reading
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.