[KNOX-1645] Improve JSESSIONID handling

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Assignee: Kevin Risden
• Reporter: Kevin Risden
• Created: 29/Nov/18 20:30
• Updated: 28/Mar/19 13:57
• Resolved: 30/Nov/18 15:07

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.

Issue Links

• is duplicated by: KNOX-654 Support configurable session cookie name and possibly change default
• is related to: KNOX-1364 Cookie scoping path should contain the topology name
• relates to: ATLAS-1420 Change Atlas cookie name to ATLASSESSIONID instead JSESSIONID
• relates to: RANGER-981 Change session cookie name from JSESSIONID to RANGERADMINSESSIONID
• relates to: KNOX-653 Support rewriting cookie names
• relates to: ZEPPELIN-3897 Customize JSESSIONID cookie name to avoid conflicts