[
https://issues.apache.org/jira/browse/KNOX-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787255#comment-16787255
]
Martin Ruskov commented on KNOX-1783:
-------------------------------------
Yes, you are right. They are separate tasks. But I wouldn't open a second Jira
for now, would prefer to keep it here.
Regarding the original task, my current problem is that Superset redirects all
other calls to the login page. And the login page doesn't submit the login
request properly, so requests always end up being redirected to a wrong address
that is composed of Knox's domain and Superset's request path. I suspect this
might be a problem, related to handling of slashes (as in [#KNOX-899]).
One way to do the SSO integration could be, however, implementing handling [in
Superset|https://flask-appbuilder.readthedocs.io/en/latest/security.html#your-custom-security]
JWT tokens generated [by
KNOX|https://svn.apache.org/repos/asf/knox/site/books/knox-0-9-0/knoxsso_integration.html].
> Proxy support for Superset UI
> -----------------------------
>
> Key: KNOX-1783
> URL: https://issues.apache.org/jira/browse/KNOX-1783
> Project: Apache Knox
> Issue Type: Improvement
> Reporter: Martin Ruskov
> Assignee: Martin Ruskov
> Priority: Minor
> Fix For: 1.3.0
>
>
> Provide proxy UI support for the Superset UI.
>
> To my understanding, this is a matter of adding a [new
> service|https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.5/bk_security/content/adding_new_service_knox_gateway.html]
> to the KNOX gateway, but there seem to be problems with trailing slashes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
