[
https://issues.apache.org/jira/browse/KNOX-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated KNOX-1645:
-------------------------------
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.
was:Knox sets JSESSIONID and this can cause conflicts with services that also
use JSESSIONID.
> 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 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)
