Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
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
Attachments
Issue Links
- is duplicated by
-
KNOX-654 Support configurable session cookie name and possibly change default
- Closed
- is related to
-
KNOX-1364 Cookie scoping path should contain the topology name
- Closed
- relates to
-
ATLAS-1420 Change Atlas cookie name to ATLASSESSIONID instead JSESSIONID
- Resolved
-
RANGER-981 Change session cookie name from JSESSIONID to RANGERADMINSESSIONID
- Resolved
-
KNOX-653 Support rewriting cookie names
- Open
-
ZEPPELIN-3897 Customize JSESSIONID cookie name to avoid conflicts
- Open
Initial patch to try to change the JSESSIONID cookie name to KNOXJSESSIONID. This should avoid conflicts with other services that use JSESSIONID.