Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-36960

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

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Low Engagement
    • None
    • 3
    • 13

    • 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.

    Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA 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 JIRA session cookie by modifying the $JIRA_INSTALL/conf/context.xml to the following (or something similar):

      <Context sessionCookieName ="JIRASESSIONID">

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

      Additional workarounds can be found within User is Constantly Logged out of JIRA.

      Attachments

        Issue Links

          is related to

          Suggestion - JRACLOUD-62886 Update our installation documentation to be clearer about multiple instances

          • Closed

          Suggestion - JRASERVER-36960 Configure Tomcat so that it has a unique SESSION_COOKIE_NAME to prevent session overwriting for JIRA

          • Gathering Interest
          was cloned as

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

          • Gathering Interest

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: