GitHub user prasadwagle opened a pull request: https://github.com/apache/incubator-zeppelin/pull/681
Notebook Authorization ### What is this PR for? The goal of the PR is to add authorization for notebooks according to the design document [here] (https://gist.github.com/prasadwagle/712b7ca1e0f1f4f1aa20). ### What type of PR is it? Feature ### Todos * [ ] - Investigate how to use Shiro authorization * [ ] - Use groups associated with user to determine if operation is permitted * [ ] - Add authentication for the rest api call to set permissions * [ ] - Add checks in more NotebookServer operations * [ ] - Improve UI (explain permissions, error messages) * [ ] - Add unit tests * [ ] - Documentation ### Is there a relevant Jira issue? ZEPPELIN-549 ### How should this be tested? 1. Create a note. By default all operations are allowed by any authenticated user. 1. Update readers, writers and owners by clicking on the lock icon in the top right area. 1. Check if users can or cannot perform operations according to the permissions. ### Screenshots (if appropriate)  ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? No You can merge this pull request into a Git repository by running: $ git pull https://github.com/prasadwagle/incubator-zeppelin notebook_authorization Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-zeppelin/pull/681.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #681 ---- commit 6e85730343399c174090d2cf329bc3407d12e142 Author: Prasad Wagle <pwa...@twitter.com> Date: 2016-02-01T06:30:51Z Notebook Authorization ---- --- 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. ---