Details
-
Improvement
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
As a Zeppelin admin user, I want to control who can/cannot edit the interpreter settings in a particular Zeppelin instance.
Taking a similar approach to "Notebook Authorization", we should include logic in the interpreter settings code so we have more control on what users are allowed or not to change.
Initial requirements:
- Should validate updates (UI -> REST API -> Validate)
- Should integrate with Shiro (via SecurityUtils)
- Persistence in conf/interpreter.json file
Given your experience moon, zjffdu, felixcheung, please let me know any initial feedback you have on this. Thanks!
Attachments
Attachments
Issue Links
- links to