Thursday, December 23, 2010

EJBCA 4.0 alpha1 released

Hi everybody!

Eagerly waiting for the next major version of the best PKI software in the world? Now is your chance to try it out.

EJBCA 4 uses Java Enterprise Edition 5 (JEE5) instead of J2EE. This is a major improvement of the core, modularization, portability and packaging, but you will not notice many functional differences.

What else?

  • The database schema is fully defined through the Java Persistence API and table create scripts are provided for all the supported databases.

  • Many bugs have been corrected. For example EJBCA Services will run more stable in a clustered environment.

  • The Ingres database can now be used with EJBCA without patching the code.

  • A JEE5 compliant application server, Java 1.6 and Ant 1.7.1 or higher is required from this version on.

Since this is and alpha release, you can expect a few rough edges. Have in mind that there will not necessarily be an upgrade path from this release to EJBCA 4.0.0.

Submit bug reports!

Happy holidays and testing,
The PrimeKey EJBCA Team

EJBCA 3.11.1 released

Today PrimeKey has released EJBCA 3.11.1.

This is a maintenance release – 16 issues have been resolved. Only fixes
and layout improvements, no new features.
This release fixes an upgrade issue from 3.6.x to 3.11.x and also a
MySQL/MyISAM related issue in the 3.11.0 release.
A few uncaught regressions from 3.10.x and 3.11.0 were fixed, and as
usual David Carella of Linagora added some Admin GUI layout improvements.

Noteworthy changes:

  • It is now possible to easily upgrade from EJBCA 3.6.x to 3.11.x.

  • Fixed a MySQL mapping that did not work when using the MyISAM storage engine and UTF-8 encoding.

  • ETSI QC value limit can now have the value zero.

  • Admin GUI improvements from David Carella of Linagora.

  • Added a favicon to the EJBCA web interfaces.

  • Fixed an issue causing cached end entity profiles (not default) to be changed for some actions in the admin GUI.

  • Fixed an issue where session information spilled over to other edits when using the "Back to certificate profiles" link.

  • Fixed an issue where using the required flag on Cardnumber in a end entity profile gave error about missing unstructured address. This also resolved an issue where the DN field Unstructured Address did not work.

You can read the full changelog in the EJBCA Jira.

In addition to making EJBCA available as full open source software, PrimeKey also supplies support services and training for EJBCA.

Wednesday, December 1, 2010


Next year at FOSDEM in Brussels, 5-6 february 2011, we will do something different. Previous years we have had a stand, but this year we will participate in the OpenSC devroom.

Anyone interested in PKI and smart cards (and any of the other hundreds of open source technologies present at FOSDEM) should go there.

See you in Brussels!