Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-79031

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Low Low
    • None
    • 7.13.7, 7.18.1
    • Data Center - Core
    • None

      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

            [CONFSERVER-79031] confluence.cluster.authentication.secret system property is not given precedence over confluence.cfg.xml

            James Ponting added a comment -

            Hi All,

            I'm going to close this issue as Not a Bug and explain why.

            The intent of this functionality is for it to be configured through the confluence.cfg.xml file. In some cases we also provide a route to configure such options as a system property. In this case we did not implement the system property, but mentioned it in the documentation provided to our technical writers. As a result it was erroneously added to the Recognized System Properties page.

            We've removed the references to this system property, and are in the process of creating documentation for how to change the properties and set configuration in the confluence.cfg.xml file.

            As this was never intended to be a system property, it not working is not a bug and I've closed it out.

            Our apologies for the confusion.

            Thanks,
            James Ponting
            Engineering Manager - Confluence Data Center

            James Ponting added a comment - Hi All, I'm going to close this issue as Not a Bug and explain why. The intent of this functionality is for it to be configured through the confluence.cfg.xml file. In some cases we also provide a route to configure such options as a system property. In this case we did not implement the system property, but mentioned it in the documentation provided to our technical writers. As a result it was erroneously added to the Recognized System Properties page. We've removed the references to this system property, and are in the process of creating documentation for how to change the properties and set configuration in the confluence.cfg.xml file. As this was never intended to be a system property, it not working is not a bug and I've closed it out. Our apologies for the confusion. Thanks, James Ponting Engineering Manager - Confluence Data Center

              Unassigned Unassigned
              caronson Cole Aronson
              Affected customers:
              1 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: