GitHub user prabhjyotsingh reopened a pull request: https://github.com/apache/zeppelin/pull/2058
[ZEPPELIN-2147] zeppelin should redirect to login page after browser session expires ### What is this PR for? Zeppelin should redirect to login page after browser session expires ### What type of PR is it? [Bug Fix] ### What is the Jira issue? * [https://issues.apache.org/jira/browse/ZEPPELIN-2147](https://issues.apache.org/jira/browse/ZEPPELIN-2147) ### How should this be tested? - Open any Zeppelin's notebook on a browser - Restart zeppelin server - now as soon as next web-socket message or API request is sent to server that returns either "ticket is invalid" or 405. This should get redirected to login page. - On successful login it should take user back to the page from where he was coming from. ### Screenshots (if appropriate) ![zeppelin-2147](https://cloud.githubusercontent.com/assets/674497/23250873/ec27b6e6-f9d0-11e6-8e6f-75e97f2449b1.gif) ### Questions: * Does the licenses files need update? N/A * Is there breaking changes for older versions? N/A * Does this needs documentation? N/A You can merge this pull request into a Git repository by running: $ git pull https://github.com/prabhjyotsingh/zeppelin ZEPPELIN-2147 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2058.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 #2058 ---- commit 918908903125a7a4d3fef645174153cf62530c29 Author: Prabhjyot Singh <prabhjyotsi...@gmail.com> Date: 2017-02-23T08:13:18Z in case of session lost or logout, show login window commit 27bc361415c792f8666a9a67a423150d5887f0e6 Author: Prabhjyot Singh <prabhjyotsi...@gmail.com> Date: 2017-02-24T07:31:10Z user $timeout with $location ---- --- 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. ---