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 GitHub Bot (JIRA)" <ji...@apache.org> on 2019/03/29 18:54:00 UTC

[jira] [Work logged] (KNOX-1835) Jupyter Enterprise Gateway - KERNEL_USERNAME should be added when not present

     [ https://issues.apache.org/jira/browse/KNOX-1835?focusedWorklogId=220664&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-220664 ]

ASF GitHub Bot logged work on KNOX-1835:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Mar/19 18:53
            Start Date: 29/Mar/19 18:53
    Worklog Time Spent: 10m 
      Work Description: risdenk commented on pull request #79: KNOX-1835 JKG KERNEL_USERNAME should be added when not present
URL: https://github.com/apache/knox/pull/79
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 220664)
    Time Spent: 1h 10m  (was: 1h)

> 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
>             Fix For: 1.3.0
>
>         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)