EJBCA Installation Prerequisites
- EJBCA Community 18.104.22.168
- Quick Install Guide
- Ubuntu 18.04 (Bionic Beaver)
- VirtualBox 6.0
EJBCA Install Instructions
For the most part this will be extracted from the link above provided by PrimeKey but there will be some small amendments. Most notably the amendments are related to a bug in the guide.
- Install Ubuntu, and create a directory in the home of the user and name it “Opt”. In my example, I created a user called “user”, so the full path once the directory is created, is.
- Run an update on the system to ensure everything is up to date and nothing is running on older legacy versions.
sudo apt-get update
- Now install the prerequisites that PrimeKey recommend, see the command below.
sudo apt-get install unzip openjdk-8-jdk-headless ant ant-optional psmisc mariadb-client bc patch curl
- Unfortunately by default java will run in a version that EJBCA will not co-operate with, so we need to change the java version running. To do this run the following command and the version will change to 1.8.
sudo update-java-alternatives --set java-1.8.0-openjdk-amd64
- Next thing to do, is perform a check to ensure that java has changed or you’ll get errors later in the guide.
sudo java -version
- Download EJBCA from the link above, move this to the directory we created /home/user/Opt/ in this example.
- Unzip the EJBCA download and to the same location. You should now have a folder similar to /home/user/Opt/ejbca_xxxx
- Install MariaDB, this is not included in the primekey guide, so perform the following.
sudo apt-get install mariadb-server
9. Once installed, we need to log into the mysql server running via mariadb. Once logged in, you will need to create a database and provide access to a set of credentials. See instructions below.
sudo mysql -u root -p
mysql> CREATE DATABASE ejbcatest CHARACTER SET utf8 COLLATE utf8_general_ci;
mysql> GRANT ALL PRIVILEGES ON ejbcatest.* TO 'ejbca'@'localhost' IDENTIFIED BY 'ejbca'
- Ignoring step 4 in the PrimeKey instructions, because this is just a sample setup. We don’t need to configure any file for database password or user because they’re defaulted in there and the same as the above section, we have just done in mysql.
MAJOR BUG: https://jira.primekey.se/browse/ECA-8667
11. Now we need to detour from the EJBCA PrimeKey guide because there is a bug in the community version 22.214.171.124 being used here. We need to open a terminal and browse to the following location.
sudo nano build.xml
12. Browse through the file that has just opened, in nano and locate the section that starts naming targets. We need to amend the “Build the Sun P11 extension” section. In Nano to save time you could press ctrl+w and type Sun P11 and it will save you time finding it. Once found we need to update the line in the file to make this check optional.
<target name="cesecore-p11" description="Build the Sun P11 extension">
<target name="cesecore-p11" description="Build the Sun P11 extension" if="build.cesecore.p11.jar">
- Save the file. Now return to the /home/user/Opt/ directory.
- Remain within this directory and run the following command. Do not run this as sudo or it will fail immediately.
- A few minutes will pass and then hopefully you will be presented with a location for the P12 file, which is /home/user/Opt/ejbca_xxxx/p12/ and a password for its usage. These will be within the terminal and a local website address.
- We need to import the .p12 file that has been created in to Firefox, so open the browser and then select edit > preferences. In the new window that appears look for privacy and security, then click on View Certificates. Click on the “Your Certificates” tab and then press the import tab.
- In the import window that now appears, simply browse to the location of the .p12 file and select it. You may have to change the file type to “all files”. Once selected, a window will appear prompting for the password. Copy this from the terminal or notepad if you saved it and click ok.
- Browse to the local address provided https://localhost:8443/ejbca/adminweb/ and you should see EJBCA load.
Note: When you restart Ubuntu, this will fail to load by default because the services are not running. To fix this you need to start up WildFly again and this can be done by the following.
19. Now you need to check that the file “standalone.sh” is in this directory and run it.
20. If you’re to be running this sample/example version of EJBCA over a longer period because you want to perform some thorough exploration, then the best thing to do is write a cron job to start the service as soon as the system loads. This can be done through the following commands.
21. Open cron – in a terminal type
22. In the screen that appears, scroll to the bottom and type
23. Save the file and then close.
24. Reboot the system and see if everything loads up normally.