EJBCA Cert-Manager Issuer

A cert-manager CertificateRequest controller that issues X.509 certificates from an EJBCA certificate authority, for Kubernetes clusters requiring…

  • Infrastructure
  • Security
  • Tools & Utilities
A cert-manager CertificateRequest controller that issues X.509 certificates from an EJBCA certificate authority, for Kubernetes clusters requiring enterprise-grade PKI.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • 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.

62/100 Good

Maintained
75last commit 10 days ago
Popular
2313 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
100128 MB minimum RAM, runs on ARM
Security check
94no serious findings, 1 minor, CI, tests
GitHub stars
13
Open issues
12
Last commit
2026-11-11
Latest release
ejbca-cert-manager-issuer-2.2.2
License
Apache-2.0
Activity
rising

Checked 3 days ago - source: GitHub (Keyfactor/ejbca-cert-manager-issuer)

Resources & Compatibility

Minimum requirements: 128 MB RAM. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Fill install.properties before installing Create the install.properties file with your CA name, admin user, server hostname, and key settings, and replace the example passwords. If these values are missing or left as weak defaults, the installation can fail or give you an insecure, hard-to-use CA. source
  • Start p11-kit only if using a hardware token Run the p11tool and p11-kit commands on the computer with the USB token, then export the P11_KIT_SERVER_ADDRESS path it prints (an environment variable pointing to the local socket). This makes the hardware token reachable; without it EJBCA cannot see the private key and certificate signing breaks. source
  • Run pest client setup before enrolling Run the pest client's cacerts command against the server's EST enrollment address to fetch the CA certificate before enrolling anything. If the client does not have that certificate first, enrollment or certificate requests can fail trust checks. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What Docker image name should self-hosters use for this cert-manager issuer?

Use the Docker image keyfactor/ejbca-cert-manager-issuer. Problem reports and feature suggestions are directed to GitHub issues.

What connection issue has been reported when testing the cert-manager Issuer and ClusterIssuer with EJBCA?

Users have reported that the Issuer and ClusterIssuer cannot connect to the EJBCA instance, so they cannot issue certificates.

Which EJBCA install.properties fields must be set before installation?

Set the CA name, admin user, server hostname, and key settings, and replace example passwords. Missing values or weak defaults can make installation fail or leave the CA insecure.

How should a USB hardware token be made reachable for EJBCA signing?

Run the p11tool and p11-kit commands on the machine with the token, then export the printed P11_KIT_SERVER_ADDRESS environment variable to the local socket. Without it, EJBCA cannot see the private key and certificate signing breaks.

What pest client step must be completed before EST enrollment?

Run the pest client's cacerts command against the server's EST enrollment address to fetch the CA certificate first. If the client lacks that certificate, enrollment or certificate requests can fail trust checks.

What may happen if EJBCA adminweb is accessed too early?

It can return unauthorized responses. One reported fix was deleting the datadbdir directory and recreating it.

Answers sourced from docs.keyfactor.com, docs.keyfactor.com, docs.keyfactor.com, github.com, hub.docker.com, www.reddit.com

Community

Collected 48 days ago - public community threads