You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2019/03/29 18:52:00 UTC
[jira] [Assigned] (KNOX-1835) Jupyter Enterprise Gateway Dispatch
Handler
[ https://issues.apache.org/jira/browse/KNOX-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Risden reassigned KNOX-1835:
----------------------------------
Assignee: Bhanu Teja (was: Kevin Risden)
> Jupyter Enterprise Gateway Dispatch Handler
> -------------------------------------------
>
> Key: KNOX-1835
> URL: https://issues.apache.org/jira/browse/KNOX-1835
> Project: Apache Knox
> Issue Type: New Feature
> Reporter: Jesus Alvarez
> Assignee: Bhanu Teja
> Priority: Major
> Attachments: KNOX-1835.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Jupyter Enterprise Gateway [https://jupyter-enterprise-gateway.readthedocs.io/|https://jupyter-enterprise-gateway.readthedocs.io/en/latest/]
> is built directly on Jupyter Kernel Gateway, for which there are service definitions available from [https://issues.apache.org/jira/browse/KNOX-976]
>
> In the same manner that Apache Livy uses "proxyUser", JEG / JKG leverage a "KERNEL_USERNAME" [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/getting-started-security.html].
>
> For requests which are Authenticated via Knox, Knox could take a similar approach to that in https://jira.apache.org/jira/browse/KNOX-1098 , and ensure this is set to the Authenticated user, whether the JEG client request has provided it in the payload or not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)