[
https://issues.apache.org/jira/browse/KNOX-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628305#comment-14628305
]
Jeffrey E Rodriguez commented on KNOX-565:
-------------------------------------------
This work is also dependent on Ambari changes.
https://issues.apache.org/jira/browse/AMBARI-12393.
My thought on changes needed for UI.
1. Open source UI's are release dependent, meaning they change from release to
release. So it is very important to document the process on how to support UI's
(vs REST). REST API's tend to change less frequently.
2. Should document the use of rewrite OUT and the different options
supported. I had to read the code and fully understand when I did the changes
to support open source UIs/.
3. think we need to investigate Xforward headers.
4. We also need to look at performance so caching web content at Knox server
maybe needed (we should add a Jira for this). REST calls don't need to cache
since they reflect the state of the data and single calls request/response,
UI's in the other hand are made in it majority on content which is static and
doesn't change, so we need common caching for web content to avoid the jump
client->knox->service for every web page.
5. All code supporting UI needs full set of unit test cases.
> 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
>
>
> 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)
