• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Upgrade
    • None
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem:

      Jira 8.6 introduced a new functionality that allows the users to migrate the existing customizations from their server.xml and setenv.sh when upgrading Jira.

      The server.xml allows the users to keep their SSL configuration(among other configurations), however by not keeping the cacerts information, all SSL connections like LDAPS, POP3S, IMAPS will be broken after the upgrade. Besides the external SSL connections, the Jira users will also experience failures in the Gadget Feed Health Check due to the loss of the trusted certificates.

      Resolution and Impact:

      By also maintaining the cacerts file after the upgrade, we will be able to provide a more seamless experience to our customers when upgrading Jira.

            [JRASERVER-70646] Maintain the bundled cacerts file when upgrading Jira

            There are no comments yet on this issue.

              Unassigned Unassigned
              abrancalhao@atlassian.com Armando Neto
              Votes:
              6 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: