EJBCA Community

The open-source public key infrastructure (PKI) and certificate authority (CA) software EJBCA is one of the longest running CA software projects.

  • Media Applications
  • Security
The open-source public key infrastructure (PKI) and certificate authority (CA) software EJBCA is one of the longest running CA software projects. EJBCA covers all your needs - from certificate enrollment, via certificate management, to certificate validation.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

13/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
351 install platform, install notes, Docker image
Light to run
2016 GB minimum RAM, runs on ARM

Based on 3 of 4 factors.

Availability: platform listings confirmed 18 days ago

No GitHub repository data collected yet.

Checked 17 days ago - source: GitHub (BigBearTechWorld/big-bear-casaos)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 8 CPU core(s), 60 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fill in install.properties first Create install.properties and replace the example values for the CA name, server password, superadmin account, and java.trustpassword before starting EJBCA. These settings create your CA and admin access, so wrong or missing values can prevent proper startup or leave you unable to manage the CA later. source
  • Make REST API port 8443 reachable The REST API examples connect to EJBCA over HTTPS on port 8443, so make sure that port is open or reachable from the machine you are testing from. If a firewall blocks it, API checks like CA status or certificate downloads will not connect. source
  • Start p11-kit for USB/HSM tokens If you are using a USB smart card or hardware security module, start the p11-kit server and use the token URL or socket path it prints. p11-kit is a helper that lets EJBCA reach the token, and without it EJBCA cannot find the key, so signing or certificate operations can fail. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What must I configure before first starting EJBCA Community?

Create install.properties and replace the example values for the CA name, server password, superadmin account, and java.trustpassword. Wrong or missing values can prevent proper startup or leave you unable to manage the CA later.

Which port needs to be reachable for EJBCA REST API calls?

Make port 8443 reachable over HTTPS from the machine testing the API. If a firewall blocks it, API checks such as CA status or certificate downloads will not connect.

What must be started when using a USB smart card or HSM with EJBCA?

Start the p11-kit server and use the token URL or socket path it prints. Without p11-kit, EJBCA cannot find the key and signing or certificate operations can fail.

Where does EJBCA store one-time passwords for new end entities?

A one-time password is stored hashed with BCrypt in the UserData table in the database.

Answers sourced from ca.mibcon.cz, docs.keyfactor.com, docs.keyfactor.com, docs.keyfactor.com

Community

Collected 48 days ago - public community threads