[
https://issues.apache.org/jira/browse/KNOX-3033?focusedWorklogId=919069&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-919069
]
ASF GitHub Bot logged work on KNOX-3033:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/May/24 11:57
Start Date: 13/May/24 11:57
Worklog Time Spent: 10m
Work Description: stoty commented on PR #912:
URL: https://github.com/apache/knox/pull/912#issuecomment-2107383158
I have followed up on this, and this won't work with some service
definitions.
A few service definition, like hbaseui 2.1.0 have a template in the metadata
context field.
AFAICT this never gets used anywhere, as up until now context was just an
informative field, but this means that my current patch is guaranteed not not
work with those services.
Either
* We need to change the context field for those context values for a
non-templated one
* We need to find/define another field to use for the cookie context
* We need to determine the context some other way like calculating a prefix
of all route entries.
Issue Time Tracking
-------------------
Worklog Id: (was: 919069)
Time Spent: 20m (was: 10m)
> Add option to set the correct path for sticky session cookies instead of
> appending the role name
> ------------------------------------------------------------------------------------------------
>
> Key: KNOX-3033
> URL: https://issues.apache.org/jira/browse/KNOX-3033
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I have tried to override the sticky session cookie name by using the
> following HA parameter:
> {noformat}
> <param>
> <name>WEBHBASE</name>
>
> <value>enableStickySession=true;noFallback=true;enableLoadBalancing=true;stickySessionCookieName=STICKYCOOKIE</value>
> </param>
> {noformat}
> However, KNOX still appended the service name to the cookie name:
> {noformat}
> 24/04/30 08:25:11 DEBUG http.wire: http-outgoing-0 << "Set-Cookie:
> STICKYCOOKIE-WEBHBASE=58d004bcaccfddfdc69739ea053505c69b2679d6fc1da6f7e46d3907be2d1e6c;
> Path=/gateway/cdp-proxy-api-stoty; Secure; HttpOnly[\r][\n]"
> {noformat}
> AFAICT the point of overriding the cookie name would be integrating with
> other components (like a cloud LB) that expect a specific cookie name.
> Appending the service name after the specified cooke name defeats this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
