IMPORTANT:After upgrade of Advanced Authentication 5.1.3 with already configured repositories to 5.2, open Repositories section and click Sync now button for the configured repositories. Wait few minutes while synchronization is performed.
To check for updates open the Advanced Authentication Administrative Portal and switch to Updates section. You may get a list of operating system updates, because Advanced Authentication checks for these updates automatically. To check for the Advanced Authentication Server updates, please click Check for updates button.
NOTE:Operating systems updates must be applied before the Advanced Authentication Server updates.
IMPORTANT:Upgrade must be done in period of lowest users/ security officers activity and in shortest time period. It's recommended to minimize the time period when Advanced Authentication DB Master server is upgraded, but the DB Slave servers are not, because replication of non-synced DBs may break the DB Slave servers.
To perform the update please follow the instruction:
Make snapshots for all Advanced Authentication servers. Try to do it in minimal time period.
Stop load balancer, or if you don't use it turn off the Advanced Authentication DB Slave server, turn off the Advanced Authentication Member servers.
Upgrade the Advanced Authentication DB Master server, restart it.
IMPORTANT:After upgrade of DB Master to v5.2 it's required to log on to web services of DB Slave and Member servers using uppercase name of repository and user name. E.g. LOCAL\ADMIN or ADMIN. When the upgrade is done you will be again able to use lower case names. The user names and repository names in v5.2 are not case sensitive.
Turn on the Advanced Authentication DB Slave server one-by-one and upgrade it, restart it.
Turn on the Advanced Authentication Member servers one-by-one and upgrade them, restart them.
Start load balancer.
Wait for 20 minutes when all servers are upgraded and check the Farm Servers tab in Administrative Portal on both the DB Master and DB Slave Servers to ensure that the replication still works. In case of problems with replication, reinstall DB Slave Server.
Ensure that the users are still able to authenticate on their endpoints.
Upgrade plugins if applicable.
Upgrade few test endpoints and use them during few days, collecting a feedback.
Upgrade the rest endpoints.
IMPORTANT:You may get the error "Configured and running. Replication conflict. Fix: stop replication and reinstall DB2 server" on the Farm servers section. To fix this it's required to re-install the Advanced Authentication DB Slave server.