Upgrading from a Release < 20.9.1.0
Condition
The actual eperi sEcure Platform version is behind 20.9.1.0 and it is going to be upgraded.
Cause
Changes in product.
Remedy
Procedure
-
Perform the upgrade as described in the eperi sEcure Platform
Administrator Manual, section Operational Tasks > Upgrading to a new release.
Important: Due to the default SSL/TLS configuration of the Admin Console the server.xml file has changed. When you perform the upgrade on Ubuntu, you will be asked, if you want to keep the existing server.xml. If you already have installed your own TLS certificate and have configured the Admin Console to use TLS, you might keep the existing server.xml. On a RHEL/CentOS machine the new server.xml will be filed as server.xml.rpmnew. There you need to adjust the server.xml manually.
-
If you are using the eperi Milter app: Due to the
default SSL/TLS configuration of the Admin Console, it is necessary to import
the pre-configured TLS certificate into the truststore of the eperi Milter app as follows:
Important: This will only work if the eperi sEcure Platform and the eperi Milter app are installed on the same machine and the eperi sEcure Platform can be accessed by the name 'localhost' which is the hostname included in the preconfigured SSL/TLS certificate. Otherwise a certificate matching the hostname of the eperi sEcure Platform machine has to be created and imported.
- Get the SSL keystore and password from the server.xml file (Port 8443 Connector).
-
List the content of the keystore file (and search for the alias
name):
keytool -v -list -keystore /path/to/keystore.p12 | grep -i alias -
Export the certificate by alias name:
keytool -export -alias <alias> -file <certname>.cer -keystore /path/to/keystore.p12 -
Import the previously exported certificate into the Java Truststore
used by the eperi Milter app:
keytool -import -alias <new_alias> -keystore /opt/eperi/milter/java/jre/lib/security/cacerts -file <certname>.cer
-
Consider to replace the pre-configured TLS certificate with your own TLS
certificate as described in section Replacing the pre-configured TLS certificate
with your own certificate in the eperi sEcure Platform Admin
Manual.
Note: If you do that, you must also import your certificate into the eperi Milter app as described above.
