EJBCA
EJBCA is a fully functional Certificate Authority in Java using J2EE technology. It builds on the J2EE platform to create a robust, high performance, platform independent, flexible, and component-based CA to be used standalone or integrated in any J2EE app. EJBCA comes with a flexible and powerful Web-based admin GUI.
| Licenses | LGPL |
|---|---|
| Operating Systems | OS Independent |
| Implementation | Java |
Recent releases
- 05 Jun 2009 10:27
Changes: Support was added for DSA keys. A republishing mechanism for robust publishing was added. Many improvements were made to OCSP with on-line renewal of keys. Performance was improved. The admin GUI was improved. Lots of fixes were made.
- 28 Mar 2009 00:35
Changes: This is a minor release adding improvements and bugfixes. Street and pseudonym DN attributes have been added. There are OCSP improvements, RFC 5019, nextUpdate, support for requests using GET, and improved configuration and error handling. Correct coding of optional Issuing Distribution Point in CRLs. The ability to publish userPassword in LDAP. A few minor fixes.
- 29 Jan 2009 14:20
Changes: Broken support for Glassfish was fixed. Support for JBoss 5.0 was added. Support for Weblogic 10.3 was improved. IPv6 subject alternative names were fixed. A few minor bugs were fixed.
- 15 Dec 2008 14:28
Changes: Administrator validation was restructured to allow adminstrators to use externally issued certificates. The administrator flag was dropped in end entities. Support for SEIS Card Number extension was added. KRB5PrincipalName subjectAltName was added. A command to list objects in a Luna HSM partition was added. It is possible to sign releases and deployed code.
- 18 Nov 2008 15:15
Changes: Email from- and to- is also substituted in user notifications. The default ENDUSER Certificate Profile was fixed. A built-in Server certificate profile was created. External RA SCEP service fails on a Cisco message with a wrongly encoded request extension. The missing ErrorCode class in ejbca-util.jar was replaced. OCSP should not respond with responseBytes when an error code is sent. OCSP responder should answer with OCSP error MalformedRequest when a badly encoded request is received.
