Uploaded image for project: 'Jira Cloud (including JIRA Core)'
  1. Jira Cloud (including JIRA Core)
  2. JRACLOUD-36960

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



    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.


      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.


          Issue Links



              • Assignee:
                dcurrie@atlassian.com David Currie
              • Votes:
                68 Vote for this issue
                47 Start watching this issue


                • Created: