Upgrade from 6.15.2 to 7.10 - need advise/help

[s0p4LiN]

Hello, I could not find any information on google so I come here.

In may 2020, I had installed EJBCA 6.15.2.6 Community (r34564) for the company I work for.
I was in apprenticeship at the time and did not wrote any documentation. I've just followed at the time followed these guides: https://fladnag.net/?page_id=104 as the PrimeKey documentation was too difficult to understand.

But now, the Certificate Authority is used by all of our Internal Web Services and I want to upgrade it as it been 2 years in production already.

EJBCA were installed on an Debian 10 with:

• Wildfly 10.1.0
• openjdk-8-jdk
• mariadb Ver 15.1 Distrib 10.5.9-MariaDB

I want to upgrade EJBCA first, and then migrate it to an Ubuntu 22.04 LTS Server.

Here's the files in my ejbca-custom folder:

ejbca.properties
database.properties
crlstore.properties
cesecore.properties
certstore.properties
web.properties
install.properties
batchtool.properties
mail.properties

I tried to follow the official documentation for upgrading the production server, but if I'm stuck at merging *.properties files, I do not understand the terms.

Do I need to add all new line from the *.properties files that comes from the 7.10 versions into my current *.properties files and then continue the upgrade with ant deployear ?

Also, do I need to upgrade OpenJDK and Wildfly after EJBCA upgrade ?

And last question, for the databases script update, which one do I need to use ?
If im logical, I would say the scripts in 615_70, but as I see folder 790_7100, it means the scripts in the folder 615_70 helps upgrading from v6.15 to v7.0 but not to v7.10 ?

Thank you

[mike-agrenius-kushner]

Hi,

I'd say https://doc.primekey.com/ejbca/ejbca-installation/upgrading-ejbca is fairly straight forward, but to be clear:

1. You don't need to touch the property files at all. The beauty of having them in ejbca-custom means that 7.10 will just source them from there when constructing the EAR
2. If your wildfly user has create rights to your database, you likewise need to do nothing – EJBCA will create all the new tables/columns for you and update any needed data. Afterwards you'll need to run the post-upgrade from the UI – this removes old data from the database and exists to allow multiple EJBCA versions in a cluster to run against the same database during upgrade.

So all you need to do is run ant deployear from the main directory of EJBCA 7.10, which needs to be placed in the same directory as ejbca-custom.

Cheers,
Mike

[s0p4LiN]

[s0p4LiN]

I did just relaunch again the Post Upgrade and it worked, I think there was some timeout during the 7.4.0 --> 7.10 in the first time and that is why It failed (I presume).

Anyway, It is upgraded ! Yeah !

What are the nexts steps ? Can I upgrade Wildfly ? OpenJDK ? Mariadb without issue ?

[mike-agrenius-kushner]

Hi,

Love to see it.

Yeah, you're free to upgrade all of the above, though be aware that for the moment our JDK17-support is still a bit spotty, so I recommend sticking to JDK11 until the next major coming out in the spring.

Cheers,
Mike

[s0p4LiN]

Tank you for you help I will upgrade it.

[s0p4LiN]

Last question:

Is it normal that it display now Working Copy ?

[mike-agrenius-kushner]

Yeah, that just shows that it's a release and not a direct checkout from Git.

Cheers,
Mike

[s0p4LiN]

alright, thank you very much ! I will now write a documentation for my company before leaving and advise them to take the Enterprise Subscription for the ACME auto enroll feature...