Hi
@Rick Bowden,
Upgrade on AWS doesn't require going through Support for Upgrade Validation,
since it is included in the procedure performed using the command:
impctl platform import.
Regarding the "secure" user password, you are right, starting version 14.1 password must contain at least one special character.
If the password is different in the new MX, the upgrade will probably fail.
I'm still checking, but according to the information I have right now, the passwords should patch on both MXs.
I'll update you with the additional information soon.
Thanks,
------------------------------
Ira Miga
Imperva
Knowledge Engineer
------------------------------
Original Message:
Sent: 01-25-2021 05:31
From: Richard Bowden
Subject: Upgrading The WAF MX and the Secure Password
We are in the process of upgrading from WAF (SecureSphere) version 12.5 to 14.3 on AWS using the on demand marketplace AMI.
I have a question regarding the secure password and the export/import process.
I understand that I have to raise a support case to have the 12.5 export upgraded to 14.3.
We have created a new 14.3 server in readiness for importing this.
The new 14.3 has been created with a new secure password that is different from the one used to create the 12.5 version, as it seemed prudent to create a stronger password than the 12.5 version has currently.
Will this cause issues for the upgrade?
Does the upgraded database still have the old secure password?
#On-PremisesWAF(formerlySecuresphere)
------------------------------
Richard Bowden
Aviva
------------------------------