In EJBCA 6.12-6.14 we accidentally broke compatibility with certificate profiles from earlier versions, when using database protection. This change was reverted in EJBCA 188.8.131.52 (
ECA-7277), and special code was added to be compatible with the broken versions.
This compatibility code reads the certificate profiles in a way that triggers an automatic upgrade. Now that we add new fields to certificate profiles (and hence a new version, triggering an upgrade), we must bypass the upgrade.
This does not affect any released versions, only SVN. But it is causing a test failure in Eca7277RegressionTest.certificateProfileCreatedInEjbca614Verifies on Jenkins.