Customers are adviced not to move to SF 5.8.0 HF-2 or SF 5.8.0 HF-3 to avoid a few known issues in those versions and wait till SF 5.8.0 HF-4 is released.

The following enhancement that was added in SF 5.8.0 HF-2 to address a customer requirement, 
"SF-9983 - Password appears in clear text for AD and DB users in silver fabric."
inadvertently resulted in a few other issues under the following scenarios:

1. When using a failover broker setup, the failover broker would not be able to connect to DB when the primary goes down.
2. Migration from 5.8.0 HF-2/HF-3 to Future SF 5.8.1 would not work unless some manual steps are performed.

Customers who are already on SF 5.8.0 HF-2/HF-3 on a primary-failover setup can work around the first scenario by maintaining the same encrypted password for both the primary and failover Broker. Following manual steps are required to be performed to resolve this issue,

• Shutdown the failover broker.    - Locate the installation.properties file (typically [FABRIC_ROOT]/fabric/webapps/livecluster/WEB-INF/config/installation.properties) 
• Locate a property named “DSInternalDBPassword” in the installation.properties file. 
• Set the value of DSInternalDBPassword to be same as that of primary (copy the value of DSInternalDBPassword  from primary broker’s installation.properties file).
• Start the failover broker. 
• Primary broker restart is NOT required.

    
To address the second scenario, when upgrading to a future service pack like SF-5.8.1 from SF 5.8.0 HF-2/HF-3, customers will need to move to SF-5.8.0 HF-4 first before upgrading to the service pack. 

SF-5.8.0 HF-4 would be released soon to address this problem in couple of ways,

• Make encryption optional and not mandatory.5.8.0-HF4 will have a property called “DSPasswordEncryption” in installation.properties which will control the  encryption of passwords.   
• Change the encryption algorithm to produce matching encrypted passwords for primary and failover broker

To avoid the inconvenience, if customers who are currently considering to move to SF 5.8.0 HF-2/HF-3 can wait till SF 5.8.0 HF-4 is released and move to SF 5.8.0 HF-4 at that point, it will make a future upgrade to SF 5.8.1 a smooth process as before. The problematic HFs SF 5.8.0 HF-2/HF-3 have been taken down from the customer hotfix download site to prevent customers from downloading them till we release SF 5.8.0 HF-4.
 

Customers are adviced to not move to SF 5.8.0 HF-2 or SF 5.8.0 HF-3 to avoid a few known issues in those versions and wait till SF 5.8.0 HF-4 is released.