You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/03/29 18:54:00 UTC
[jira] [Commented] (KNOX-1835) Jupyter Enterprise Gateway -
KERNEL_USERNAME should be added when not present
[ https://issues.apache.org/jira/browse/KNOX-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805340#comment-16805340 ]
ASF subversion and git services commented on KNOX-1835:
-------------------------------------------------------
Commit 6d05bb882a78403470d161a7f7116a147b69fb0a in knox's branch refs/heads/master from Bhanu Teja Allaparthi
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=6d05bb8 ]
KNOX-1835 - Jupyter Enterprise Gateway - KERNEL_USERNAME should be added when not present (#79)
> Jupyter Enterprise Gateway - KERNEL_USERNAME should be added when not present
> -----------------------------------------------------------------------------
>
> 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 10m
> 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)