Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-36960

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

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Feedback Policy:
      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 An updated workflow for server feature suggestions.
    • UIS:
      37

      Description

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

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dcurrie@atlassian.com David Currie
              • Votes:
                137 Vote for this issue
                Watchers:
                75 Start watching this issue

                Dates

                • Created:
                  Updated: