Github user echarles commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Whatever `su` or `ssh` is used, I feel the main trick is the user
provisioning on the host running the interpreter. Until now, the shiro
authentication system had no impact on the user provisioning. This PR changes
this.
I guess we all agree and are aware that adding user `foo` to shiro.ini, and
enabling impersonation, will require to run `adduser foo` manually.
We should make this clear in the doc but also stress it in the UI (with a
hover, or a clear text/link near the <checkbox> User Impersonate.
---
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.
---
