[
https://issues.apache.org/jira/browse/KNOX-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704872#comment-16704872
]
ASF subversion and git services commented on KNOX-1645:
-------------------------------------------------------
Commit 19b1d75bcb50f92a1768f8c92dd3ac35a30200dc in knox's branch
refs/heads/v1.2.0 from [~risdenk]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=19b1d75 ]
KNOX-1645 - Improve JSESSIONID handling
Signed-off-by: Kevin Risden <[email protected]>
> Improve JSESSIONID handling
> ---------------------------
>
> Key: KNOX-1645
> URL: https://issues.apache.org/jira/browse/KNOX-1645
> Project: Apache Knox
> Issue Type: Bug
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Blocker
> Fix For: 1.2.0
>
> Attachments: KNOX-1645.patch, KNOX-1645.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
