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

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

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 6
    • 7
    • We collect Confluence 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? 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.

          Form Name

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

            k a added a comment -

            Trial version of Jira can't work at the same time as the trial version of Confluence without a dive into the forums.

            k a added a comment - Trial version of Jira can't work at the same time as the trial version of Confluence without a dive into the forums.

            This issue is known since 5 Years? Really? and not yet resolved? seems to be a simple patch, but why is this issue still pending?

            No hint in the official documentation.. Sorry, but i thought this is an enterprise tool

            Christian Barchfeld added a comment - This issue is known since 5 Years? Really? and not yet resolved? seems to be a simple patch, but why is this issue still pending? No hint in the official documentation.. Sorry, but i thought this is an enterprise tool

            Nathaniel Compton added a comment - - edited

            Enterprise level customer. 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.

            Nathaniel Compton added a comment - - edited Enterprise level customer. 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.

            +1 This is very easy to fix on Atlassians side and shouldn't have any negative side-effects for users that don't have a multihomed environment.

             

            Christian Keck added a comment - +1 This is very easy to fix on Atlassians side and shouldn't have any negative side-effects for users that don't have a multihomed environment.  

            Zaakiy Siddiqui added a comment - - edited

            I followed the instructions however there was an undocumented permissions issue when installing using the default Jira and Confluence paths. (JIRA first, Confluence second)

            To resolve this, I enabled "Other" to have r-x access to the following folder (has to be other since user is confluence and group is root)
            chmod 776 /var/atlassian/application-data/

            My workaround is not perfect but it's the best I can do without breaking anything. So please Atlassian, provide a fix for this. Thanks in advance.

            Zaakiy Siddiqui added a comment - - edited I followed the instructions however there was an undocumented permissions issue when installing using the default Jira and Confluence paths. (JIRA first, Confluence second) To resolve this, I enabled "Other" to have r-x access to the following folder (has to be other since user is confluence and group is root) chmod 776 /var/atlassian/application-data/ My workaround is not perfect but it's the best I can do without breaking anything. So please Atlassian, provide a fix for this. Thanks in advance.

            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:
              93 Vote for this issue
              Watchers:
              60 Start watching this issue

                Created:
                Updated: