[jira] [Commented] (KNOX-1645) Improve JSESSIONID handling

["Kevin Risden (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KNOX-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707687#comment-16707687 ] 

Kevin Risden commented on KNOX-1645:
------------------------------------

Found that Atlas and Ranger have both changed JSESSIONID cookie names due to similar issues.

> 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)