Uploaded image for project: 'Apache Knox'
  1. Apache Knox
  2. KNOX-1645

Improve JSESSIONID handling

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.2.0
    • Component/s: None
    • Labels:
      None

      Description

      Knox sets JSESSIONID and this can cause conflicts with services that also use JSESSIONID.

      Found while testing 1.2.0rc2 with Knox and multiple services. If you visit /yarn/ and then visit /zeppelin/ you will not be able to stay logged into Zeppelin. The issue is that Knox sets a JSESSIONID with a cookie path /gateway/TOPOLOGY. Zeppelin tries to set its JSESSIONID cookie on path / but the Knox JSESSIONID cookie is more specific and is picked up first. This means that the login is successful but the next activity in Zeppelin requires a second login again.

        Attachments

        1. KNOX-1645.patch
          3 kB
          Kevin Risden
        2. KNOX-1645.patch
          3 kB
          Kevin Risden

          Issue Links

            Activity

              People

              • Assignee:
                krisden Kevin Risden
                Reporter:
                krisden Kevin Risden
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: