Software Upgrade
Important: Before upgrading the device, we recommend performing a backup of your device. The procedure is described in this guide.
Note: Secfense User Access Security Broker is an isolated, on-prem device. This means it does not perform any automated upgrades. In order to obtain the image with new version you need to contact your Secfense representative
Note: If you are running an instance with a customized look of the user interface, remember to backup the
/secfense/app/shared/internalauth_public_custom
folder.
Upgrading the single node setup:
This procedure describes upgrading the Secfense Broker in a single node installation. Please note that during this upgrade, a short downtime in service will occur.
Important: Before version 15.3.5 you need to run the script
bin/upgrade
from CLI between steps 4 and 5
- Download the file with new software.
- Log in to the Secfense Broker administration panel.
- Navigate to the Releases section in the left-hand menu and enter maintenance mode by clicking Enable in the upper right corner.
- Click "Add new release" – wait until the file is uploaded. Once the upload is finished, an "install now" button will be available in the list of available releases.
- Click "Install now" next to the chosen release. The process should take several minutes, and once it's finished, the version should be updated.
- Exit maintenance mode.
Upgrading the clustered setup:
Important: Before version 15.3.5 you need to run the script
bin/upgrade
from CLI between steps 4 and 5
- Download the file with new software.
- Log in to the Secfense Broker administration panel.
- Navigate to the Releases section in the left-hand menu and enter maintenance mode by clicking Enable in the upper right corner.
- Click "Add new release" – wait until the file is uploaded. Once the upload is finished, an "install now" button will be available in the list of available releases.
- Click "Install now" next to the chosen release. The process should take several minutes, and once it's finished, the version should be updated.
- Repeat steps 2 to 5 on the second node.
- Exit maintenance mode on both devices.
In a scenario where two devices are clustered, it is impossible to exit maintenance mode when devices are running different software versions.