Describe the bug
When logged in as a user, the NotebookSocket associated with your session gets a "user" property with your username.
If you then log out and log in as a different user without refreshing the login page or fully closing your browser, the "user" property of your NotebookSocket will stay the same as it was during the first login.
Expected behavior
NotebookSocket's "user" property should change on login so that there is no stale data within the NotebookSocket.
How to reproduce
Log in to Teragrep
Check your NotebookSocket's user property
Log out
Log in as a different user
NotebookSocket's user property has not changed
Software version
Zeppelin Server v0.10.1-rc2-fs-build-5
Desktop (please complete the following information if relevant):
Browser: Firefox
Additional context
Checking the NotebookSocket's user property can be done by adding a line of code printing it into Zeppelin's logs after login
Describe the bug When logged in as a user, the NotebookSocket associated with your session gets a "user" property with your username. If you then log out and log in as a different user without refreshing the login page or fully closing your browser, the "user" property of your NotebookSocket will stay the same as it was during the first login.
Expected behavior NotebookSocket's "user" property should change on login so that there is no stale data within the NotebookSocket.
How to reproduce
Software version Zeppelin Server v0.10.1-rc2-fs-build-5
Desktop (please complete the following information if relevant):
Additional context Checking the NotebookSocket's user property can be done by adding a line of code printing it into Zeppelin's logs after login