You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2019/05/24 00:41:00 UTC

[jira] [Updated] (HBASE-22467) WebUI changes to enable Apache Knox UI proxying

     [ https://issues.apache.org/jira/browse/HBASE-22467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated HBASE-22467:
-------------------------------
    Attachment: HBASE-22467.001.patch

> WebUI changes to enable Apache Knox UI proxying
> -----------------------------------------------
>
>                 Key: HBASE-22467
>                 URL: https://issues.apache.org/jira/browse/HBASE-22467
>             Project: HBase
>          Issue Type: Improvement
>          Components: UI
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Major
>         Attachments: HBASE-22467.001.patch
>
>
> Apache Knox's gateway is nice in that it can provide centralized authentication and authorization for a collection of service. Additionally, it can expose "private" nodes through a single point (e.g. a gateway). This makes our life as developers much easier in cloud deployments where it's not straightforward to access nodes (e.g. they're running on some private network).
> KNOX-1866 captures the changes over there required to make HBase's proxying actually work (definition lives there), but there were a few things we do in our UI which made it hard/impossible to proxy it correctly.
>  * ProfilerServlet was dropping extra query parameters in the URL
>  * JSON task output on master/regionserver couldn't be disambiguated
>  * Some missing /master-status and /rs-statusĀ links couldn't be disambiguated properly due to a lack of context
>  * Missing content-type set on a profiler servlet response



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)