Upgrade
The SAS solution can be deployed in varying configurations. The instructions included in this documentation are based on a generic SAS PCE deployment as depicted in the following diagram, independent of the deployment strategy defined by the customer’s specific needs:
The adaptation of the generic deployment to the custom requirements of each site (data center) is determined by your deployment team.
Note
It is mandatory to stop all BlackShield and SAS services before performing the MySQL Server upgrade. Additionally, no actions should be performed on the SAS side during the database upgrade process.
Note
- Starting with SAS-PCE 3.22, it is recommended to delete existing SAS database users and replication users and recreate them using the caching_sha2_password authentication plugin in MySQL Workbench.
- Starting with MySQL 8.0.3x, MySQL introduced full support for the caching_sha2_password plugin. This plugin is the default authentication method in MySQL versions 8.4 and later.
However, user who wants to use MySQL server 8.0.25, it is necessary to explicitly specify the caching_sha2_password plugin in the script while creating MySQL users.
For example,
CREATE USER 'SAS DB User'@'IP address of the SAS server' IDENTIFIED WITH caching_sha2_password BY 'password'; GRANT ALL PRIVILEGES ON *.* TO 'SAS DB User'@'IP address of the SAS server';
Supported Versions
This documentation describes how to upgrade from SafeNet Authentication Service (SAS) PCE versions 3.8 (and later) to the latest version.
Before upgrading from any previous version to SAS PCE latest version, refer the System Requirements section to check if all the required prerequisites are available.
Refer to the below sections for more details:
