[
https://issues.apache.org/jira/browse/KNOX-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627503#comment-14627503
]
Tanping Wang commented on KNOX-565:
-----------------------------------
Kevin Minder While we were under the mission of delivering the UI work through
Knox with limited time constrain, redirecting was the only solution that we
found currently would fits the situation. We felt the PAIN while implementing
this. And we see that this could not be sustainable. We have this picture of
Knox being the centralized (client) proxy, not only for REST calls, or UIs but
also possible extend to other protocols, e.g. IPC/RPC, JDBC. Extending Knox to
support all the UIs is only the first step. We can certainly talk about this
more in details. With the current Knox framework, what would be your idea in
order to support UIs going through Knox proxy? If there is no good Java based
streaming JavaScript parser as you also noted, this is the only solution that
we can think of.
> Supporting All the Quick Links on Ambari Dashboard to Go Through Knox
> ---------------------------------------------------------------------
>
> Key: KNOX-565
> URL: https://issues.apache.org/jira/browse/KNOX-565
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 0.7.0
> Reporter: Tanping Wang
> Attachments: KNOX-565 - UI support design.pdf
>
>
> Today Knox supports authentication and service level authorization for rest
> APIs. We have a need to have all of the user interfaces to also go through
> Knox. So that Knox can become the single hub for all https communications
> including both UIs and rest calls.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
