[GitHub] zeppelin issue #1223: [WIP Zeppelin-945] Interpreter authorization
Github user astroshim commented on the issue: https://github.com/apache/zeppelin/pull/1223 I'll do this at the another PR. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1223: [WIP Zeppelin-945] Interpreter authorization
Github user astroshim commented on the issue: https://github.com/apache/zeppelin/pull/1223 @prabhjyotsingh Thank you for share your great idea. This PR is for interpreter authorization but your idea seems include user management. I think it should be separated and I agree with @Leemoonsoo's idea of giving the same user experience for the authorization inside of Zeppelin. and I also agree with @prabhjyotsingh's idea of the difference with notebook's because interpreter authorization is n:n. (it's hard to show with notebook's way.) so What do you guys think about following way? - when you want to grant permission of interpreters to all users  - when you want to grant permission of interpreters to specific user  --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1223: [WIP Zeppelin-945] Interpreter authorization
Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/1223 @Leemoonsoo I would say, since the use case for this is different than that of notebook, and idea for this is to map access to users with interpreters. While reading the title/description of this PR this is what I had in my mind  Also think about the case where user is getting auth using LDAP/AD where there are 100s of user, so this will require pagination. So, we need to have a group/profile for users that can have preset for grouping interpreters together.  And once this is set, IMO, then user who don't have permission to a particular interpreter, should not see that interpreter in the notebook page. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1223: [WIP Zeppelin-945] Interpreter authorization
Github user astroshim commented on the issue: https://github.com/apache/zeppelin/pull/1223 @Leemoonsoo Thank you for your review and I think your opinion makes sense. I'll change the UI. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1223: [WIP Zeppelin-945] Interpreter authorization
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1223 @astroshim Thanks for the contribution. Regarding UI, why don't we use the same UI with notebook authorization? That can give the same user experience for all the authorization inside of Zeppelin. Than it'll look something like  What do you think? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
