I'm sorry. I now realise that I made a mistake while trying to execute a workaround due to a clumsy copy-paste, causing it to fail. So while this bug is still real, it is not fatal. Barrier can still be made to work.
in the Barrier SSL folder on the Barrier server, and then to restart the Barrier service using the Barrier interface on the server. I did this in MacOS, but I believe that the exact same command will work for Ubuntu, except that the path to the Barrier SSL folder will be different.
I'm sorry. I now realise that I made a mistake while trying to execute a workaround due to a clumsy copy-paste, causing it to fail. So while this bug is still real, it is not fatal. Barrier can still be made to work.
The workaround is to execute the command
openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem
in the Barrier SSL folder on the Barrier server, and then to restart the Barrier service using the Barrier interface on the server. I did this in MacOS, but I believe that the exact same command will work for Ubuntu, except that the path to the Barrier SSL folder will be different.