Find out which version you run, prepare for an upgrade, and keep client tools in step with the server.
Hover over the version in the profile menu of the header bar to see the product version. The portal footer shows the frontend and backend versions. For release 3.02.01, the versions are:
| Component | Version |
|---|---|
| Product | 3.02.01 |
| Backend | 3.02.01 |
| Frontend | 3.03.01 |
Read the Release Notes for every version between yours and the target version.
Create a backup, download it, and store it off the server. See Backup.
Confirm that your HSM backup is current.
Record the current product, frontend and backend versions.
Plan a maintenance window. Signing is unavailable while the server restarts.
Tell approvers and pipeline owners when signing will be unavailable, and pause automated pipelines.
Encryption Consulting provides the upgrade package and the step-by-step procedure for each release. Contact support before you start, and don’t run a new installer over an existing installation unless the release instructions tell you to.
Sign in and check the version shown in the profile menu and the footer.
Check that HSM Health Check is Active.
Download the client tools again from Signing Tools and update your build machines.
Run a test signing with each client tool you use, then resume pipelines.
Use the client tools published with your server release, which are the ones on your own server’s Signing Tools page. After a server upgrade, update the KSP, EC KSP for Mac, PKCS#11 Wrapper, Utility Tool and ec-signer on your build machines.
The PKCS#11 Wrapper now caches the signing key and can take the key label from an environment variable or the configuration file. No configuration change is required, because automatic key label detection stays on by default. See PKCS#11 Wrapper.