Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-32589

Configure Tomcat so that it has a unique SESSION_COOKIE_NAME to prevent session overwriting for Confluence

    • 1
    • 5
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      When multiple applications are configured on the same domain with separate ports, users will be constantly logged out of each application as the SESSION_COOKIE_NAME is identical.

      This is due to the Tomcat configuration. Please alter the default bundled Tomcat 7 config so that it has a unique Confluence session cookie by modifying the <CONFLUENCE_INSTALL>/conf/context.xml to the following (or something similar):

      <Context sessionCookieName ="CONFSESSIONID">
      

      This will prevent users from getting into this problem in the first place.

      Additional workarounds can be found within Logging into Another Atlassian Application Logs Me Out of Confluence.

            [CONFCLOUD-32589] Configure Tomcat so that it has a unique SESSION_COOKIE_NAME to prevent session overwriting for Confluence

            Enterprise level customer here, have been paying for years. We continue to experience this issue. Gitlab and Github both have this issue sorted out. The only thing preventing us from canceling our Jira contract and moving to another vendor is the Jira ticket history. But even that is because less and less valuable of an argument.

             

            Hopes remain high that your team corrects this seemingly simple fiasco. 

            Nathaniel Compton added a comment - Enterprise level customer here, have been paying for years. We continue to experience this issue. Gitlab and Github both have this issue sorted out. The only thing preventing us from canceling our Jira contract and moving to another vendor is the Jira ticket history. But even that is because less and less valuable of an argument.   Hopes remain high that your team corrects this seemingly simple fiasco. 

            This is so annoying and the jira and confluence installs are so much slicker now. Every time I install I have to do this.

            Francis Pindar added a comment - This is so annoying and the jira and confluence installs are so much slicker now. Every time I install I have to do this.

            F added a comment -

            The problem is not only present with Atlassian product, but also with other product, like Teamcity. It could be a good improvement for a small modification.

            F added a comment - The problem is not only present with Atlassian product, but also with other product, like Teamcity. It could be a good improvement for a small modification.

              Unassigned Unassigned
              dcurrie@atlassian.com Dave C
              Votes:
              36 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated: