[
https://issues.apache.org/jira/browse/KNOX-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450286#comment-16450286
]
Larry McCay commented on KNOX-1274:
-----------------------------------
Sure.
You can work on a rewrite rule for the Location header - look at other
service definitions like Ambari - I think they rewrite redirects.
In the meantime, since you are proxying as well as using SSO, you can use
the SSOCookieProvider as Sandeep mentioned.
As long as it supports trusted proxies, it should work fine - if it doesn't
then you will need to use the Hadoop provider and get the rewrite rule done.
> SSO redirect for Spark2 History Server needs to be rewritten
> ------------------------------------------------------------
>
> Key: KNOX-1274
> URL: https://issues.apache.org/jira/browse/KNOX-1274
> Project: Apache Knox
> Issue Type: Bug
> Reporter: Marco Gaido
> Assignee: Sandeep More
> Priority: Major
>
> When Spark2 History Server is accessed through Knox gateway and Knox SSO is
> configured, after the authentication, the SSO redirects to the direct Spark
> History Server's URL, instead of the proxied one, ie. one gets redirected to:
> {{https://knox_host:8443/gateway/knoxsso/knoxauth/login.html?originalUrl=http://shs_host:18081/&do....}}
> and so after the login, it redirects to {{http://shs_host:18081/&doAs=...}},
> instead of {{https://knox_host:8443/gateway/default/sparkhistory}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
