Compatible with
account required
EJBCA / Keyfactor
EJBCA REST enrollment, certificate search, renewal and revocation are implemented, plus ACME aliases when enabled on the CA. Profiles and CAs are discovered rather than typed as opaque IDs.
Verification: test_verified. Connection: unknown. Credentials: none. Live E2E: no.
EJBCA host and client certificate are not configured.
What sslcertificates.io can do
EJBCA REST enrollment, certificate search, renewal and revocation are implemented, plus ACME aliases when enabled on the CA. Profiles and CAs are discovered rather than typed as opaque IDs. Capabilities: rest, acme, profiles, enroll, renew, revoke. Authentication uses client_certificate.
Required permissions
EJBCA REST or ACME alias with a client certificate. Profiles must allow the sslcertificates.io enrollment user.
Setup
Open Dashboard → Integrations → EJBCA / Keyfactor. Enter the credentials described on this page. Values are encrypted at rest and never shown again. Run Test connection. Discovery runs only after authentication succeeds. Select a discovered resource. Do not paste opaque IDs unless the provider cannot enumerate them. Perform the certificate or notification action, then confirm the external system matches. Disconnect removes stored credentials and owned test resources created by sslcertificates.io.
Known limitations
Live E2E needs an EJBCA instance. Public internet enrollment is not assumed.
Official sources
Fact checked 2026-09-20. https://doc.primekey.com/ejbca/ejbca-operations/ejbca-ca-concept-guide EJBCA / Keyfactor is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.
Capabilities
Connect
EJBCA / Keyfactor is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.