EJBCA CE
Official Keyfactor Helm chart that deploys EJBCA Community Edition, a self-hosted public key infrastructure (PKI) and certificate authority (CA) solution, on…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- 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.
55/100 Fair
- Maintained
- 83last commit 82 days ago
- Popular
- 60970 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- 1016 GB minimum RAM
Availability: platform listings confirmed today
- GitHub stars
- 970
- Open issues
- 20
- Last commit
- 2026-08-31
- Latest release
- r9.6.3
- License
- LGPL-2.1
- Activity
- stale
Checked 14 days ago - source: GitHub (Keyfactor/ejbca-ce)
Resources & Compatibility
Minimum requirements: 16 GB RAM, 8 CPU core(s), 70 GB disk.
Checked 41 days ago - source: Docker Hub image tags and published docs
First-install notes
- Fill in install.properties before starting Create the install.properties file (the setup sheet) with your certificate authority (CA) name, HTTPS hostname, and admin details before starting EJBCA. If values are missing or copied from examples, EJBCA may use the wrong address or you may be left with an easy-to-guess password. source
- Keep the API HTTPS port open The examples call the REST API (software requests) at https://localhost:8443, so open or map that HTTPS port if other machines need to reach EJBCA. If it is blocked by Docker or a firewall, API clients get connection errors instead of certificate or status data. source
- USB HSM? Start p11-kit first If you are using a USB hardware token, run the p11-kit command and copy the token URL it prints before connecting EJBCA to it. p11-kit is a helper that makes the local token visible to Linux, and skipping it can make the token appear missing. source
- Not for production use EJBCA Community Edition is not intended for production use; for production PKI deployments use Keyfactor EJBCA Enterprise Edition. source
Fetched 41 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Is EJBCA Community Edition intended for testing and prototyping PKI workflows?
Yes. The repository describes EJBCA CE as an open-source subset of EJBCA Enterprise and says it is designed for learning, testing, and prototyping certificate and PKI workflows.
What UEM integration issue affects EJBCA CA names?
UEM can remove spaces from the CA name when SAN attributes are used. The discussion also covers troubleshooting UEM integration with EJBCA and a workaround.
Can EJBCA be used for additional subordinate CAs in a Microsoft AD CS homelab?
A Reddit user who set up an intermediate Microsoft AD CS CA for autoenrollment considered adding an EJBCA instance for a few extra subordinate CAs.
Where are the EJBCA install, setup, and release notes?
The EJBCA learn page provides release notes and documentation for installing, setting up, and using EJBCA. It also points to video tutorials and discussion forums.
Answers sourced from community.omnissa.com, github.com, www.ejbca.org, www.reddit.com
Community
Collected 48 days ago - public community threads