confluence.cluster.authentication.secret system property is not given precedence over confluence.cfg.xml

Issue Summary

According to Recognized System Properties, confluence.cluster.authentication.secret and confluence.cluster.authentication.enabled can be configured via system property. The confluence.cfg.xml value will always overwrite the secret configured via system property.

Steps to Reproduce

1. Stop all nodes
2. Remove confluence.cluster.authentication.enabled and confluence.cluster.authentication.secret entries in all node confluence.cfg.xmls and the shared home
3. Configure the properties via Configuring System Properties
   • Tested using a Linux box and setenv.sh entries
4. Start up one of the nodes

Expected Results

1. The secret used by the application becomes the value set as a system property

Actual Results

1. The system properties are read in as noted in > General Configuration > System Information
2. A new secret different from the system property entry is generated in confluence.cfg.xml

Workaround

Configure the secret via confluence.cluster.authentication.secret in confluence.cfg.xml