GitHub user sravan-s reopened a pull request:
https://github.com/apache/zeppelin/pull/2087
[ZEPPELIN-2172] Redirect to home if notebook authentication fails in
realtime
### What is this PR for?
Redirect to home page, if a user declines the access failure message on a
notebook
### What type of PR is it?
[Bug Fix]
### What is the Jira issue?
* [ZEPPELIN-2172](https://issues.apache.org/jira/browse/ZEPPELIN-2172)
### How should this be tested?
1. Create a notebook with qa_user user as the owner
2. Give write permissions to user test_user1, and read permissions to user
test_user3
3. Now in another tab, open the notebook with test_user1 user who has write
permissions
4. In the original tab, have user qa_user (owner of the notebook) remove
the write permissions from test_user1 user and grant it to some other user
test_user5.
5. Goto the other tab where user test_user1 was logged in. It shows an
error message
6. On click of close button, UI should redirect to homepage
### 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/sravan-s/zeppelin ZEPPELIN-2172
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2087.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 #2087
----
commit b73cc7364bf0121ff26a7599198f7365cccad92c
Author: ess_ess <sravans2...@gmail.com>
Date: 2017-03-01T15:11:39Z
[ZEPPELIN-2172] Redirect to home if auth fails
If someone restricts the access to a notebook in
realtime, show proper error messsage. If user
chooses not to login, redirect to home 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.
---
