[
https://issues.apache.org/jira/browse/KNOX-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640945#comment-14640945
]
Kevin Minder commented on KNOX-565:
-----------------------------------
[~crystal_gaoyu] < I've set this up and played with at the HDFS, HBASE and
Oozie UIs. As expected, they all worked fine. I've also spent some time
considering the routes you've chosen and I don't see any compelling reason to
change them. The one thing I would "nit pick" is the name discrepancy between
the role=HOBHISTORYUI" and the directory name
.../data/services/mr-jobhistoryui. In spite of the pre-existing problem with
yarm-rm/RESOURCEMANAGER they should ideally match just to avoid confusion. Is
there a compelling reason you chose to have them not match?
> 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
> Fix For: 0.7.0
>
> Attachments: KNOX-565 - UI support design.pdf, KNOX-565-001.patch,
> KNOX-565-002.patch, KNOX-565-003.patch, UTResult2.out, UTRresult.out
>
>
> 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)
