Uploaded image for project: 'Zeppelin'
  1. Zeppelin
  2. ZEPPELIN-3897

Customize JSESSIONID cookie name to avoid conflicts

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      I found this while looking into issues when proxying Zeppelin through Knox (KNOX-1645). Since the JSESSIONID cookie name is generic, multiple web services on the same host can end up with the same cookie name. Ranger (RANGER-981) and Atlas (ATLAS-1420) have had to make similar changes as well.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. KNOX-1645 Improve JSESSIONID handling

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. ATLAS-1420 Change Atlas cookie name to ATLASSESSIONID instead JSESSIONID

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. RANGER-981 Change session cookie name from JSESSIONID to RANGERADMINSESSIONID

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              krisden Kevin Risden
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: